Ad platforms

Google Ads (Data Manager API)

Send outcomes to Google Ads (Data Manager API) through the approval gate, matched by click id or hashed email and phone.

Live

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Conversions > Destinations: Connect signs in with the platform (one sign-in also serves ad cost import).
Conversions > Destinations > Google Ads (Data Manager API): Google Ads customer ID (digits, no dashes); Conversion action ID; Manager (MCC) customer ID (optional); OAuth client ID (stored encrypted); OAuth client secret (stored encrypted); OAuth refresh token (datamanager scope) (stored encrypted).
Then send a test event and check Conversions > Audit log.

What OrcLink reads

Ad cost: imported by API in Conversions > Ad costs (campaign, ad group and keyword, with impressions and clicks), once a day while the scheduled jobs ad-spend and jobs run (your OrcLink operator schedules them). Cost days are the ad account's calendar days (in the ad account's time zone); conversion and outcome days are UTC days. Near midnight, a cost and its conversions can be on different days.

What OrcLink writes back

Conversions for the stages you set to relay (Outcomes > Stages), each with its click id and the hashed email and phone the platform matches on. Each batch waits for approval when approval is on (the default).

Never stored

Raw email or phone: only hashes leave OrcLink.
Page paths, page titles, referrers and IP addresses: never sent to an ad platform.