Meta Ads
Working
Meta is the advertising destination. wesaw sends eligible conversions through Conversions API and keeps the response, timestamp and event identifier in a receipt. Its browser and server paths share an event identifier. What Meta accepts, what wesaw observes and what Meta ultimately attributes remain separate statements.
What connects?
You connect a Meta dataset in wesaw. Connection options depend on your permissions and the Meta app's configuration. Credentials stay on the server. Advertising report access requires separate permissions: a working Conversions API connection does not by itself grant access to Ads Insights.
What gets sent?
A conversion event with its identifier, timestamp, value and available matching signals. Identity fields that require hashing are normalised and hashed on the server. Server-side dispatch requires recorded consent to be granted; other consent states do not authorise an upload.
How do browser and server signals work together?
wesaw's browser and server emissions use the same event identifier for a purchase. Review existing purchase senders during setup so they do not emit unrelated duplicates. wesaw can show that both paths were recorded; Meta decides whether to merge them.
What can I verify in a receipt?
The destination, recorded attempts, timestamps, response codes and any returned error. New attempt history also records the event count accepted by the destination and its trace identifier when supplied. An acceptance is labelled as a destination response, not as an attributed purchase.
What can wesaw not verify?
The final browser/server merge or purchase attribution inside Meta is not observable per event through this receipt. Event Match Quality is not a live per-event metric here. Ads Insights figures, when available, remain platform-reported figures rather than wesaw-verified campaign attribution.
Last reviewed: