Upload offline conversions from Google Sheets or CSV

The sheet layout that works

One row is one sale or one step in a sale. Keep the header row in plain lowercase, and format every column as plain text before you paste anything in. That single habit prevents most upload problems.

• email: the customer's email address, no spaces.
• phone: with the country code, for example +14155550137. Format the column as text, or the plus sign and leading zeros disappear.
• event: the stage, such as lead, booked, won or paid.
• date and time: when the event happened, in one consistent format.
• value: the amount as a plain number, no currency symbol or thousands separator.
• currency: a three-letter code such as USD, GBP or EUR.
• order_id: your own ID for the sale. The same order ID sent twice counts once, so this is what protects you from doubles.
• click ID columns: gclid, wbraid or gbraid for Google, fbclid, fbc or fbp for Meta, ttclid for TikTok, li_fat_id for LinkedIn, msclkid for Microsoft, rdt_cid for Reddit. Format as text. A click ID that a spreadsheet turns into a number or scientific notation cannot be matched.

You do not need every column. DataCops recognises many common column names, so a sheet exported from your CRM usually works with little or no renaming.

Four checks before you upload

Spend two minutes on these and you avoid most rejected rows.

1. Every row has an email or a phone number, ideally both. A row with neither cannot be matched to anyone.
2. Phone numbers carry the country code and click ID columns are set to text, so nothing was reformatted on the way in.
3. Duplicates are gone. Give every sale an order ID, and remove rows for the same sale that appear twice.
4. Dates are honest. The event dates are real, and you know which platform limits they fall inside: 7 days for Meta, 90 days after the click for Google Ads.

Ads Warmup: send past customers

Ads Warmup is the DataCops tool for lists. It sends known people, or an uploaded CSV, as real conversions to the ad platforms you pick. It is how you give a new ad account, or a new campaign, a head start: the platforms learn what your buyers look like before the first click.

How it works

• Upload or pick people. Upload a CSV of up to 20,000 rows, or pick people DataCops already knows from your site.
• Preview. DataCops reads the columns, cleans the details and shows a match score from 0 to 10 for each person. The score is our own estimate: an email adds the most, then phone, name, click ID, country and city. Previews last 24 hours.
• Choose the event. Lead, Purchase, CompleteRegistration, AddToCart or Schedule.
• Choose the platforms. Any of the 8 you connected. Platforms you did not pick are skipped and logged as not selected.
• Dry run, then send. A dry run is free and shows what would go out. Then one click sends the batch. If some rows fail, you can resend just those, free.

A same-day resend of the same person and event does nothing, so an accidental double upload never doubles your numbers. Preview and scoring are free on every plan. Sending needs the Business plan ($59 a month, $49 yearly) or Organization ($359 a month, $299 yearly). Read more on Ads Warmup.

The one thing to remember

A warmup list is sent today. It is right for a customer list you want the ad platforms to learn from now, and wrong for pretending old sales happened this week. Platforms also apply their own lookback windows, so very old sales may be refused. Send recent customers for the strongest signal.

The live feed: send new sales as they happen

For sales you add from today, skip the upload. Add each new row to the sheet, and let Google Sheets, Zapier, Make or n8n post it to your private DataCops sales webhook or the conversions API. DataCops sends it the same day.

Each post needs the event name and an email or phone. Value, currency, an order ID and click IDs are optional. Every post is logged in plain words: sent, not sent, duplicate, ignored or rejected. The same messageId sent twice counts once, so a Zap that fires twice is harmless.

The live feed has one more advantage: DataCops can join the row to the visitor it already saw on your site. The script keeps each ad click on your own domain, and a buyer who gives the same email can be linked to that first click. So a sheet row with only an email can still reach the platforms with the original click ID.

Which route, past customers or new sales?

• A one-off list of customers you already have: Ads Warmup CSV.
• Every new sale from now on: the live feed by webhook.
• Both: most teams do both. Warm up once, then keep the feed running.

If your sales already live in HighLevel, you do not need a sheet at all: the free DataCops app sends booked, showed and won stages on its own. See HighLevel conversion tracking.

The platform time limits

Meta rejects events sent more than 7 days after they happened. Google Ads ignores uploads more than 90 days after the click, and enhanced conversions for leads, which match on hashed email or phone, have a 63-day window. Microsoft Ads accepts events within 7 days of when they happened.

These limits are why the date column matters and why a sheet full of last year's sales does not behave like fresh conversions.

Why a monthly upload loses rows

This is a made-up example to show the arithmetic, not a customer result. A shop closes 40 sales in June. It uploads one CSV on 30 June.

The 8 sales from the last week of June are inside Meta's 7-day limit and are accepted. The 32 earlier ones are more than 7 days old, so Meta rejects them. Google Ads is kinder: all 40 are inside 90 days of the click, provided the click ID survived.

So one upload gives Meta 8 of 40 sales, or 20 percent. Sending each sale on the day it closes gives every platform all 40. The fix is not a better spreadsheet. It is a shorter gap between the sale and the send.

What happens to each row

Every row goes through the same path as any other DataCops conversion:

• Hashing. Emails, phones and names are cleaned and SHA-256 hashed before they leave our servers.
• Consent. The server re-checks consent before every send. For EU, UK and Swiss visitors DataCops saw on your site, nothing goes out until they opt in.
• One sale, one conversion. A purchase with an order ID is sent once per platform for 400 days, even if the pixel and a webhook also report it.
• Refunds. Post a refund with the order ID and Google Ads is corrected: a full refund is retracted, a partial one lowered. Meta and TikTok offer no correction call. See refunds.
• Delivery report. Per platform, see what was sent, skipped or failed, with a plain-English reason and the value sent.

The rest of the chain, once the script is on your site

A sheet is often the first step. The same DataCops account also runs the site side, so you can retire the sheet bit by bit:

• Built-in cookie banner. Shown in Europe by default, built to the IAB TCF v2.2 standard, with Google Consent Mode v2 on by default.
• Real people only. A per-platform switch, off by default, that keeps bot and datacenter traffic out of what each platform receives. VPN, proxy and Tor can be added.
• CRM sales without a sheet. DataCops can hold a lead and send it once your CRM marks it qualified. HubSpot is checked every 5 minutes, other systems use the release API, and held leads expire after 14 days. Salesforce and Pipedrive post through the webhook, directly or via Zapier, Make or n8n.
• Click fraud tools on Organization. Block bot IPs at the Cloudflare edge, and export refund evidence for Google's Click Quality form covering the last 60 days. Google decides the refund.

Good to know before you start

• DataCops takes your sheet as a CSV upload or as new rows posted by an automation.
• Ads Warmup preview is free; sending needs Business or Organization.
• Clean the list before you send: rows from a file come from you, so remove test and junk rows first.
• The Free plan includes 2,000 sessions for the site script. See pricing.