How to map (rename) events when sending them to ad platforms like Meta CAPI and Google Ads API

In Able CDP, “renaming” or mapping an event happens at different points in the pipeline. Which one you use depends on whether you want to rename the event everywhere or only for a single destination.

1. Automatic mapping (the default)

Able already automatically transforms conversion events between sources and destinations and correctly maps different events that have the same meaning across systems. For example, a Purchase coming from Stripe and a Purchase coming from WooCommerce are normalised for you before they reach Meta or Google, so in many cases you don’t need to configure anything at all.

2. Per-integration event mapping (rename for one destination)

When you add an ad-platform integration, you choose which internal event type maps to that platform’s conversion. This is the cleanest way to control the name a specific platform receives:

• Google Ads API — when you set up the Google Ads conversion tracking integration, you select the credential and pick an event type (for example, Purchase), then map it to a specific Conversion Action you created in Google Ads. Able then sends all purchases it attributes to Google Ads clicks to the Google Ads API against that action. Different internal events can be routed to different conversion actions.
• Meta Conversions API — the Meta/Facebook Conversions API (CAPI) integration has an ‘Event name’ setting. It's commonly required in regulated verticals such as healthcare, where standard conversion event names (e.g. “Lead”) must be changed so they aren’t flagged as restricted. See also complying with Meta’s tracking restrictions for healthcare advertisers for a full walkthrough for restricted advertisers.

3. The Rules section (rename or transform globally)

For anything beyond the per-integration options, use the Rules section of the Able dashboard. Rules let you manage how events are processed — you can transform or filter events based on specific criteria. This is where you would remap an incoming event type to a different name, or conditionally rename an event based on its properties, before it fans out to all of your destinations.

Which method should I use?

A practical rule of thumb:

• If you only need a different name on one platform (especially for Meta policy compliance), configure it in that integration’s settings.
• If you need the rename to apply consistently across every destination, do it once in the Rules section.

Summary

Method	Scope	Best for
Automatic mapping	All destinations	Standard events with identical meaning across sources
Per-integration event mapping	Single destination	Routing an event to a specific Google Ads Conversion Action, or a Meta policy-compliant event name
Rules section	All destinations	Renaming or conditionally transforming an event everywhere