Summary:
Our team has enhanced and optimized the first/latest attribution source bugs for Facebook conversion APIs. Now, if the fbclid is found, the data will be sent to the conversion API.
Scenario 1:
Original Behaviour:
– When a contact was created via a Facebook form submission, the initial attribution source was designated as Paid Social (Facebook). If you used a workflow with a Facebook form submission trigger, the contact would have an associated fbclid, and the workflow would send data to the conversion API (CAPI).
Additional Behaviour:
– After a certain period, that contact may have been converted to an opportunity with the addition of the add/update opportunity trigger. If you used the opportunity status trigger in the workflow to send the data to the conversion API, the contact resulting from the Facebook form submission would pass the fbclid.
Scenario 2:
Original Behaviour:
– If a contact was created via a Google ad, organic Google search, or direct traffic, the initial attribution source would be labelled as Paid Search (Google) or Direct Traffic. If, after a certain period, the contact interacted with a Facebook form and filled it out, the latest attribution would be labelled as Paid Social (Facebook), with the contact having an associated fbclid. If you ran a workflow with a Facebook form submission going to the Facebook conversion API, it would send that data to the conversion API with the fbclid.
Additional Behaviour:
– After a certain period, that contact may have been converted to an opportunity with the addition of the add/update opportunity trigger. If you used the opportunity status trigger in your workflow to send data to the conversion api, the contact resulting from the Facebook form submission would pass the fbclid.