Choose the purchase event counted for a Meta ad account

By default, Metrikia counts the standard purchase event (Purchase) for every Meta ad account. If your campaigns optimize for a custom conversion, for example a purchase isolated to one offer or one funnel, your Meta purchases and ROAS do not match what you steer in Ads Manager. This setting lets you choose, account by account, the event Metrikia counts as a purchase.

Prerequisites

• A Meta Ads account connected to Metrikia, with Sync this account turned on on the account card.
• A custom conversion that isolates your purchase, created in Meta Events Manager (Custom conversions, then Create). A custom pixel event is not enough: only a custom conversion can be chosen.
• Being the member who connected Meta, or an administrator of your workspace.

Choose the purchase event

1. Open the Meta integration page (/app/integrations/meta_ads).
2. Open the Ad accounts tab.
3. On the card of the account, open the Purchase event counted list. Metrikia then reads the active custom conversions of this account from Meta.
4. Choose your custom conversion. Its Meta type shows in brackets, for example Website purchase (PURCHASE).
5. A message confirms the change: Purchase event updated.

To go back to the default, choose Standard purchase (Purchase), default in the same list.

What Metrikia counts next

• The chosen conversion replaces the standard purchase, it is never added to it. A purchase your site sends both as Purchase and as the custom conversion is therefore counted once.
• Platform Purchases, its split into Platform Purchases (click) and Platform Purchases (no click), Platform Revenue and Platform ROAS follow the chosen conversion for this account, like the column of that conversion in your Ads Manager.
• A day where the chosen conversion did not fire counts 0 purchases, even if the standard purchase fired.
• The choice applies to this account only. Your other Meta accounts keep their own setting.
• Your CRM sales, Metrikia attribution and the events sent to Meta by conversion feedback do not change.

What about your history?

1. Right after your choice, Metrikia starts a sync: the last 37 days are recalculated with the new conversion.
2. Older days keep the event they were synced with.
3. To recalculate an older period, open the Synchronization tab, click Data retrieval date and pick a start date: Metrikia imports the history again from that date with the chosen conversion. Available from the Growth plan.

Expected result

Once the sync is done, Platform Purchases and Platform ROAS for this account match the column of your custom conversion in Ads Manager, over the same period.

Common problems

• "Meta no longer accepts Metrikia's access to this account": open the More options menu (the three dots at the top of the integration page), click Reconnect, then come back to the list. Your purchase event stays as it is until then.
• "Meta is limiting requests for this account right now": wait a few minutes, then try again.
• Your conversion is not in the list: check in Events Manager that it is not archived (Meta no longer tracks an archived conversion) and that it is available on this ad account.
• "No custom conversion on this account": create one in Meta Events Manager to isolate your purchase, then open the list again.
• Your conversion shows with its number and "(not found on the account)": the chosen conversion was archived or deleted in Meta, so it no longer reports purchases. Choose another conversion, or go back to the standard purchase.
• The list is greyed out: the sync of this account is paused. Turn on Sync this account on the account card, then choose the event.
• Your numbers have not changed yet: the sync started after your choice can take a few minutes. Follow the last sync date in the Synchronization tab.
• The change fails while Meta is connected: only the member who connected Meta, or an administrator of your workspace, can change this setting.

Missing a feature? Suggest it in Ideas and Roadmap (in Settings). A technical issue? Use Report a bug from the help menu.