Message Match: Social Proof That Fits Each Ad (UTM Guide)

Message match is the degree to which a landing page repeats what the ad that sent the visitor there promised: the same offer and the same product, in the same words. When the match is tight, the visitor knows in a second that they landed in the right place. When it's loose, they have to work it out, and many won't bother.

Most guides stop at the headline and the hero image. This one covers the part they skip: the social proof on the page. If your ad sells one boot and your notifications show orders for a random candle, the page has broken the match even if the headline is perfect.

Below: what message match covers, how to tag your ads so Fomo can tell them apart, how to show a different set of notifications to each campaign's visitors, and one setting to review so Fomo's own tracking doesn't clash with your ad's.

Key takeaways

• Message match isn't only the headline. The proof on the page should back up the same promise the ad made.
• Fomo Flows can trigger on a page path or on a UTM parameter, so each campaign can get its own sequence of notifications.
• Keep UTMs lowercase and give every campaign a distinctive name. Google Analytics treats "Meta" and "meta" as two different values.
• Fomo adds its own UTM parameters to clickable notifications. If you run ads, review them in Settings > Site so they don't clash with your ad tracking.
• Only real proof belongs on the page. Fomo doesn't do countdown timers, typed-in stock alerts or manual notifications, and that's on purpose.

What message match means (and where it breaks)

An ad makes a promise. The landing page either keeps it or doesn't. Three things need to line up:

1. The offer. If the ad says free returns, the page says free returns, near the top.
2. The words and the product. The ad's headline and image show up again on the page, so the visitor recognizes it straight away.
3. The proof. Whatever evidence the page shows (reviews, recent orders, sign-ups) is about the thing the ad was selling.

The first two are landing page basics, and we've covered them in our guide to using social proof on landing pages. The third is where most stores break the match without noticing. They set up one notification feed for the whole site, then send five different campaigns into it. A visitor who clicked an ad for running shoes gets a notification about a gift card. Nothing about it is false. It's just evidence for the wrong claim.

The fix is to treat proof the way you already treat headlines: per campaign. That's the same idea behind behavioral targeting, applied to the one thing you always know about a paid visitor: which ad they came from.

Carry the ad's proof onto the page

Start from the ad's promise and ask what real evidence would back it up. Then pick the Fomo notification that shows that evidence.

The rows below are illustrations of the pairing, not results from a real store.

Notice what's missing from the last row: an "only 3 left" alert. Fomo doesn't let you type in low-stock alerts, add countdown timers or create notifications by hand. Fomo's help center explains why: the accuracy of that kind of data is hard to enforce, and Fomo would rather protect the trust of the shoppers who see the notifications. If you want the longer argument, read why verified social proof earns more trust than generic claims.

Name your UTMs so Fomo can read them

UTM parameters are the tags you add to an ad's destination URL so your analytics knows where the visit came from. Google Analytics asks you to always use the first three below, and the other two are the ones you'll reach for most:

• utm_source: where the click came from (facebook, google, newsletter)
• utm_medium: the type of traffic (cpc, paid_social, email)
• utm_campaign: the campaign name (fall-boots)
• utm_content: which ad or creative inside the campaign
• utm_term: the keyword, for search ads

Google's guidance on naming, as of October 2026, is short: values are case-sensitive, so "Meta" and "meta" show up as two different values, and lowercase is the standard to use. You can build tagged URLs with Google's Campaign URL Builder, and the Google Analytics help page on custom campaign URLs lists every parameter.

Three habits make those tags usable by Fomo, too:

• One distinctive campaign name per ad set. Fomo Flows match on whether the visited address contains or equals your keyword. A keyword like boots would also match /pages/boots-care-guide. A keyword like utm_campaign=fall-boots won't.
• Type the keyword in Fomo exactly as it appears in the URL. Same spelling, same hyphens, same case.
• Watch out for dynamic values. If you let Google Ads fill parameters automatically with ValueTrack, a field like {campaignid} turns into a number in the live URL. Your Flow keyword has to be that number, not the campaign's name. For campaigns you want to target in Fomo, a fixed utm_campaign you wrote yourself is easier to work with.

Show different notifications to each campaign's visitors

The feature that does this in Fomo is Flows. A Flow is an ordered list of notifications that only plays on the pages you choose. Here's the setup, following Fomo's Flows guide:

1. In your Fomo dashboard, open the Flows tab and click + Add Flow.
2. Give it a name you'll recognize later, like "Fall boots, Meta".
3. Set the trigger: whether the visited address Contains or Equals your keyword.
4. Enter the keyword. It can be a page path (/pages/fall-boots) or a UTM parameter (utm_campaign=fall-boots).
5. Add the notifications you want, then drag them into the order you want them to appear.
6. Save, top right.

Each entry in the list is one spot in the queue. If you want visitors to see three recent orders in a row, add the order notification three times. Fomo fills each spot with your most recent real events.

Path or UTM: which keyword to use

If each campaign has its own landing page, key the Flow on the path. The path stays in the address as long as the visitor is on that page, whatever tags the ad added.

Key it on the UTM when several campaigns share one landing page and you need to tell them apart.

The Default Flow covers everything else

Once you enable Flows, a Default Flow plays on every page that no custom Flow targets. Before you switch Flows on, make sure the Default has a sensible general mix (recent orders, reviews), so pages you haven't set up yet still show something useful.

Keep Page Rules out of the Flow's way

Fomo's Page Rules also act on URLs. They can hide Fomo on a page, show only certain templates, or move notifications so they don't cover your add-to-cart button (Fomo's Page Rules guide). Fomo's advice is to let Flows decide the order of proof and Page Rules handle the exceptions. If a Page Rule hides order notifications on a page where your Flow puts an order notification first, the two will clash. Check both lists when you set up a campaign page.

A worked setup: one Meta ad, one landing page, one Flow

Illustration only: the store, the ad and the campaign below are made up to show the setup. No results are implied.

A boot shop runs a Meta ad: "Free returns on every fall boot." It sends the click to a dedicated page:

https://example-boots.com/pages/fall-boots?utm_source=facebook&utm_medium=paid_social&utm_campaign=fall-boots

In Fomo, the shop adds a Flow:

• Name: Fall boots, Meta
• Trigger: Contains
• Keyword: /pages/fall-boots (the page is only used by this campaign, so the path is enough)
• Spots:
  1. A Custom Roundup with the best-selling boot's product URL as the aggregate URL, so it only counts that boot's real orders.
  2. A review notification from the shop's reviews app.
  3. A recent order notification.

They also add a Page Rule to hide Fomo on /checkout, which doesn't touch the Flow's page.

The page repeats the ad's promise, and so does the proof. Every notification comes from something a customer actually did.

Keep Fomo's own UTMs from clashing with your ad's

This is the step most people miss.

By default, Fomo adds up to three UTM parameters to clickable notifications, so clicks on them show up in Google Analytics and in your Fomo dashboard. That's useful for organic traffic. For a visitor who arrived from your ad, though, a click on a notification opens the next page with Fomo's UTM values in the address, not the ad's. Fomo's help doc on Google Analytics tracking flags exactly this: Fomo's parameters can conflict with the ones from ads.

What to do, as of October 2026:

• Review Fomo's UTM fields. In Fomo, go to Settings > Site, edit or clear the UTM fields, and save.
• If you clear them, track clicks another way. Fomo's JavaScript SDK has an afterNotificationClick callback that runs every time someone clicks a Fomo notification. Use it to send a Google Analytics 4 event, or to fire a Google Tag Manager trigger. The help doc above walks through the callback.

Keep the UTMs on your ads. It's Fomo's internal tags that need adjusting, not your campaign tracking.

Check it worked: where to see the campaign

Before you spend on the ad, test it yourself:

• Open the ad's final URL in a private browser window. The first notification you see should be spot 1 of the Flow you built. If you see the Default Flow, the keyword doesn't match the address.
• Google Analytics 4: in Reports > Acquisition > Traffic acquisition, switch the primary dimension to Session campaign. Your campaign name should appear exactly as you typed it in the UTM.
• Shopify: the Shopify marketing reports show sessions and sales attributed to your marketing campaigns, and you can ask Shopify's Sidekick for the same data grouped by UTM campaign or source.

If the campaign shows up under two names (Fall-Boots and fall-boots), fix the ad's URL, not the report.

Running ads for the holidays? The same setup works for seasonal campaigns, and our Black Friday social proof guide covers what to show when traffic peaks.

FAQ

What is message matching?
Making the landing page repeat what the ad promised, so the visitor sees the offer, the product and the wording they clicked on. On a store, that includes the social proof on the page.

Can Fomo show different notifications for different ad campaigns?
Yes. A Fomo Flow plays an ordered set of notifications on pages whose address contains or equals a keyword you choose, and the keyword can be a page path or a UTM parameter.

Do Fomo's UTM parameters affect my ad tracking?
They can. Fomo adds up to three UTM parameters to clickable notifications by default, and its help center notes they can conflict with UTMs from ads. You can edit or remove them in Settings > Site.

Make every campaign page keep its promise

Message match is a promise kept twice: once in the copy, once in the proof. With Flows keyed on each campaign, Fomo handles the second half using only your real orders, reviews and sign-ups.

Take the Fomo product tour to see Flows and Page Rules in the dashboard, or compare Fomo plans. Every plan comes with a 14-day trial (as of October 2026).