Skip to content

Campaigns

The Campaigns tab lists the campaigns Pingado reads from your connected ad accounts. They appear after the account’s first sync, within the hour. For each one it shows what the ad platform reports (spend, clicks, results) next to what Pingado saw (visits, conversions, revenue), so the gap between them is easy to spot. Expand a campaign to see its ad sets (Google Ads: ad groups), and those to see their ads. Performance Max campaigns have no ad groups, so they show as one row.

  • Optimised for: the event the campaign bids on, as the Pingado event you send under that name. In Meta that is the ad set’s event; a campaign whose ad sets optimise for different events shows Mixed: compare its ad sets instead. In Google Ads it is the primary conversion actions in the campaign’s goals, when it bids for conversions. Something other than a conversion, such as link clicks or manual CPC, shows -.
  • Results: the ad platform’s count of that event. For Google Ads, the conversions of the actions Pingado sends (Google’s Conversions column, in your account’s attribution model, so it can have decimals); actions Pingado does not send, such as a GA4 import, are left out so the two numbers count the same thing.
  • Conversions: Pingado’s count of the same event, credited by last click.
  • Revenue: the value of those conversions, for purchases and renewals, next to the value the ad platform reports.

Spend is in each ad account’s own currency and is never added across currencies. Revenue is in the currency your payments came in.

Meta’s and Google’s numbers refresh every hour, down to each ad, in the ad account’s time zone. Campaign names, statuses and what they optimise for refresh every 4 hours.

Pingado ties each visit to a campaign, ad set and ad with the parameters on the ad’s link. Set them once, at the ad account level where the platform allows it.

  • IDs are the reliable part: utm_id (the campaign), pg_adset_id (the ad set) and pg_ad_id (the ad). They keep working when you rename things. No standard UTM carries ad set and ad IDs, so Pingado has its own pair, pg_adset_id and pg_ad_id.
  • Names or IDs go in utm_campaign, utm_term and utm_content (campaign, ad set, ad). Pingado matches either against the names and IDs it syncs. Ad names often repeat, so an ad matched by name alone must be the only one with that name in its ad set.

Meta (URL parameters on the ad, or Business settings for the whole account):

utm_source={{site_source_name}}&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_id={{campaign.id}}&utm_content={{ad.name}}&utm_term={{adset.name}}&pg_adset_id={{adset.id}}&pg_ad_id={{ad.id}}

Google Ads (final URL suffix, at the account level):

utm_source=google&utm_medium=cpc&utm_id={campaignid}&pg_adset_id={adgroupid}&pg_ad_id={creative}

With auto-tagging on, Google Ads needs none of these: Pingado asks Google which campaign, ad group and ad each click (gclid) came from, for clicks of the last 90 days. The parameters cover the rest, such as iPhone clicks that carry gbraid or wbraid instead of a gclid. Pingado keeps only a one-way hash of the gclid with the visit, and clears it after 90 days.

Visits that match nothing Pingado has synced are not shown in this report.