Meta
Send store events with the customer data available for matching, and read back what the campaigns spent.
- Purchase, checkout and cart events
- Shared IDs for browser/server matching
- Meta campaign spend in Attribution
Choose your metrics. Trace your conversions. See which channels bring orders.
Build a daily view around your store. Mix sales, costs and ad metrics in a section, then put them in the order you read them.
Add metrics, move cards and hide sections. Your layout is saved for the store.
Inspect payment fees, product costs and shipping. Reported and configured costs keep their source.
Inspect hourly store charts and daily ad reports. Each metric includes its calculation.
Mix store, cost and ad metrics in one custom section. Illustrative data.
Deduplication depends on each platform’s matching rules.
A browser pixel can miss an event when a page closes or a request is blocked. Your store server provides another route for the conversion.
Shared event IDs help supported ad platforms match the browser and server versions of the same purchase.
Delivery follows the consent state provided by your store integration.
Conversion delivery and reporting, with each platform’s capabilities kept clear.
Send store events with the customer data available for matching, and read back what the campaigns spent.
Use available click identifiers and hashed customer data for conversion measurement.
Send shopping events and inspect delivery to your connected Pinterest account.
Check a successful send, a temporary failure or a configuration issue. Select the examples below to inspect each outcome.
The platform accepted this event.
Select an event to inspect its delivery. Illustrative data.
Compare recorded orders and revenue, then explore the available campaign detail. Switch the grouping in this example.
| Channel | Orders | Revenue |
|---|---|---|
| Meta | 50 | €3,580 |
| Google Ads | 34 | €2,380 |
| 12 | €880 | |
| Total | 96 | €6,840 |
Store-recorded orders. Campaign detail depends on the identifiers captured.