Send additional Meta conversion parameters
Include customer details, browser identifiers, and an event ID in Skro postbacks for Meta conversion matching and deduplication.
Add supported customer and event fields to your Skro postback URL to pass additional information through the Meta Conversions API integration. First connect your Meta ad account and enable Conversions API.
Supported parameters
| Parameter | Value |
|---|---|
firstName | Customer’s first name; Roman alphabet characters are recommended. |
lastName | Customer’s last name; Roman alphabet characters are recommended. |
email | Customer’s email address. |
phone | Customer’s phone number. |
zip | Postal code in lowercase, without spaces or dashes. Use five digits for US ZIP codes; use the area, district, and sector for UK codes. |
fbLoginId | Meta app-scoped login ID. |
fbp | Browser identifier from the _fbp cookie on your domain. |
sourceDomain | Overrides the source domain sent to Meta; Skro uses the landing or offer domain by default. |
eventId | Identifies the same event across browser and server tracking for deduplication. |
Example postback
https://skrotrack.com/postback?clickId=REPLACE&payout=10&firstName=John&lastName=Doe&[email protected]&zip=12345&fbLoginId=APP_SCOPED_ID&fbp=fb.1.1596403881668.1116446470&sourceDomain=example.com&eventId=EVENT_IDReplace the example values with the data for the conversion being reported. The clickId must identify the original visit in Skro. Use your custom tracking domain in place of skrotrack.com if one is configured.
Match browser and server events
If your browser pixel and Skro report the same conversion, use the same event identifier for both copies of that event. A different conversion should have its own event identifier.
Verify the setup
Send a test conversion and compare the click ID and event ID in your tracking setup. Check that the event reaches the intended Meta pixel and contains the fields your integration supplies.
Related guides
Need help with this guide? Contact Skro support.