INSIDE TRACK ATLAS

Get to know
your next workspace.

Choose your metrics. Trace your conversions. See which channels bring orders.

FROM EVENT TO DELIVERY · EXAMPLE
Store purchase€84.90
TRACK ATLASServer-side event
YOUR SUMMARY, YOUR WAY

Keep the metrics
you actually use.

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.

Choose and arrange

Add metrics, move cards and hide sections. Your layout is saved for the store.

Know how costs are counted

Inspect payment fees, product costs and shipping. Reported and configured costs keep their source.

Read beyond the total

Inspect hourly store charts and daily ad reports. Each metric includes its calculation.

Open the full Summary demo
Choose your metricsInteractive example
My daily view4 metrics
Order revenue€6,840.00
Orders96
Google spend€840.00
Pinterest spend€280.00

Mix store, cost and ad metrics in one custom section. Illustrative data.

A purchase, from two sourcesIllustrative flow
01Browser pixelCustomer completes checkout
02Store serverPurchase reaches Track Atlas
Shared event identifierThe same purchase can be matched across sources.
Ad platformOne matched purchase

Deduplication depends on each platform’s matching rules.

FOLLOW THE CONVERSION

Two event sources.
One purchase.

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.

Keep the identifiers connected

Shared event IDs help supported ad platforms match the browser and server versions of the same purchase.

Keep consent in the flow

Delivery follows the consent state provided by your store integration.

Understand browser and server tracking
INTEGRATIONS

What connects.
And what it brings.

Conversion delivery and reporting, with each platform’s capabilities kept clear.

PlatformHow data is sentWhat you can use

Meta

Conversions API + browser pixel

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

Google Ads

Enhanced Conversions

Use available click identifiers and hashed customer data for conversion measurement.

  • Conversion delivery to Google Ads
  • Spend, clicks and CPC in Summary

Pinterest

Conversions API + browser tag

Send shopping events and inspect delivery to your connected Pinterest account.

  • Shared IDs for browser/server matching
  • Pinterest ad reports in Summary
Supported storesWooCommerceWooCommerceFunnelishFunnelishShopifyCartCore
DELIVERY DIAGNOSTICS

Find the event.
See what happened.

Check a successful send, a temporary failure or a configuration issue. Select the examples below to inspect each outcome.

Event activity3 example events
EVENT DETAILS

Accepted

The platform accepted this event.

Source
Store server
Next step
No action needed.

Select an event to inspect its delivery. Illustrative data.

CHANNEL ATTRIBUTION

Start with a channel.
Follow it to the campaign.

Compare recorded orders and revenue, then explore the available campaign detail. Switch the grouping in this example.

AttributionIllustrative data · EUR
Group by
Example orders grouped by channel
ChannelOrdersRevenue
Meta50€3,580
Google Ads34€2,380
Pinterest12€880
Total96€6,840

Store-recorded orders. Campaign detail depends on the identifiers captured.

Product, TRACK ATLAS