Conversion API

The Conversion API (CAPI) sends conversions from our server to an ad platform. The platform receives a “purchase” or “lead” event and matches it to the ad impression. No browser pixel is needed.

Not tested against live provider APIs

The sending code is written from the platforms’ public documentation, but no integration has been tested against a live provider API. The interface says the same. Before you rely on CAPI, check events with the platform’s test pixel or test mode, and confirm the event appears.

Setup

Open “CAPI integrations” (/dashboard/capi-integrations) and click “New integration”.

1. Provider. Meta, TikTok or Google Ads.
2. Credentials. The fields depend on the provider, see the tabs below.
3. Status mapping. Map our statuses to the event names of the platform, for example lead → Lead, sale → Purchase. A status with no mapping is not sent.
4. Active. Turn the integration on.

After saving, credentials are not shown. To replace them, click “Replace credentials” and enter the new values.

1. Provider.
2. The provider’s credentials.
3. The Active switch.

Providers

Meta

Field	What to enter
Pixel ID	The pixel’s ID
Access Token	A Conversions API access token

Events go to Graph API v26.0 at /{pixel_id}/events. The click stores the fbclid from the ad link. From it, an fbc value is built in the format fb.1.<time in ms>.<fbclid>. The visitor identifier is sent as the SHA-256 of our click id.

Caution

Meta accepts events no older than 7 days. If one batch contains even one older event, Meta rejects the whole batch. Late conversions and back-dated imports may fail.

Telegfy does not send the visitor’s IP address or User-Agent. So Meta’s matching is weaker than with a pixel.

TikTok

Field	What to enter
Pixel Code	The pixel code (Events API)
Access Token	An access token

Events go to Events API v1.3 (event/track). The click stores the ttclid from the ad link. It is needed for matching. Without it, the event is matched weakly.

Caution

The official TikTok documentation did not load when we checked, so the required fields are not fully verified. Check the request format with a test event.

Google Ads

Field	What to enter
Customer ID	The account ID without dashes
Conversion Action ID	The ID of the conversion action in Google Ads
Developer Token	The developer token
OAuth Client ID and Client Secret	The credentials of the OAuth app
Refresh Token	A long-lived refresh token
Login Customer ID	The manager (MCC) account ID. Optional.

Events go to Google Ads API v25 (uploadClickConversions). Telegfy gets a short-lived access token from the refresh token by itself. One rule: only a conversion with a gclid is sent. If the click has no gclid, the event is skipped.

Caution

Google Ads accepts offline conversions only for a conversion action of type “Import”. Set it up in Google Ads before you connect Telegfy. For how to obtain a refresh token, follow Google’s documentation and check each step there.

What is sent and when

• For each conversion with a mapped status, one send is created per integration. Repeats of the same pair (conversion, integration, status) are not created again.
• Sending uses the same queue as outgoing postbacks: once a minute, up to 6 attempts.
• event_id is stable across retries. The platform will not count one event twice.
• A status with no mapping is not sent, and it is not logged as an error.

Common mistakes

• No fbclid, ttclid or gclid on the click. Matching by click will not work. Check that the platform adds the parameter to the link address and that the link does not drop it on the way. Google needs auto-tagging.
• The event does not match a goal. The status mapping uses a name the platform does not know. Check the event list in the platform’s account.
• Google rejects the event. The conversion action is not of type Import, or the refresh token is out of date.

Read next

• Ad platform guides: how to pass fbclid, ttclid and gclid.
• Outgoing postbacks: the same queue and retries.
• Importing conversions: sending older conversions.