PathwAI's X integration is an X Ads Conversion API destination listed in the Data Platform catalog, where it is locked and cannot be switched on from a workspace. PathwAI does record X traffic: the twclid click parameter and UTM parameters from the landing URL are saved with each flow run. Consented events can be delivered to an endpoint you run through the Data Platform webhook destination.
What data moves
- twclid and UTM parameters from the landing URL, saved with the run.
- Through the webhook destination: mapped events with their consent state, to a URL you choose.
Where it is configured
The X Ads card appears under Data → Destinations, marked locked. Click ID and UTM capture need no setup. The webhook destination is under Data → Destinations → Webhook.
Use cases
X campaigns in funnel reports
Tag ads with utm_source=x and a campaign name to compare starts and completions by campaign.
Your own forwarding
Send consented completion events to an endpoint you run that reports them to X.
How to set it up
- Add UTM parameters to your X ad URLs.
- To forward events, add a Webhook destination under Data → Destinations and map the events.
- Ask PathwAI about the X Ads destination if you want PathwAI to deliver events.
Good to know
- The Data Platform webhook destination sends only the events you add and switch on in its Event mapping tab. With a signing secret set, each request carries an X-Pathwai-Signature header with an HMAC-SHA256 of the body, and a failed delivery is retried before it is set aside.
X integration FAQ
Does PathwAI send conversions to X?
Not directly. The X Ads destination is locked in the catalog. A webhook endpoint you run can forward events.
Is the X click ID captured?
Yes. twclid is read from the landing URL and saved with the run's attribution.
What do webhook events include?
The event name, timestamp, consent state and the properties a transformer allows.
Want to see X in a flow?
We can walk through where X fits in your funnel and exactly which data it would receive.