Crisper17 min read6 views

Conversion logs: find, export and re-send conversions

Find a lead or purchase in Crisper Logs, download the rows as Excel or CSV, and see the Meta conversions that were refused re-sent automatically.

The short answer

Open Logs, pick your dates, and search for the lead or purchase by email, phone, event or click ID. Download the rows on screen as Excel or CSV, up to 1,000. Purchases and leads Meta refused are re-sent automatically every day, up to 3 tries each, so you rarely send them by hand.

  • Find: Dashboard → choose a website → Logs, then search by event, email, phone, source or click ID.
  • Export: the download icon saves the rows on screen as Excel (.xlsx) or CSV, 18 columns, first 1,000 rows.
  • Re-send: Meta Purchase and Lead refusals from the last 6.5 days are sent again daily, up to 3 tries each.
  • Failures such as a timeout, and other events or platforms, still need Re-sync in Logs.
  • Based on Crisper's shipped Logs and Settings updates, checked 7 November 2026.

Ask an assistant

ChatGPTClaudePerplexity

FREE AUDIT

NO LOGIN

Check what Meta and Google can count on your site

  1. Your site
  2. Crisper
  3. Meta and Google count it

Enter your website to see how good its tracking is, and whether Meta is likely restricting it.

Run a free audit

Logs is Crisper's own record of each request your website sent for a lead or purchase, and where each one was delivered. When a number in Ads Manager looks wrong, you can open Logs, find the request, and see whether it reached Meta.

This page covers three jobs: finding a conversion, downloading a set of them to a spreadsheet, and what happens to the ones Meta refused. To check what Meta itself received, use How do I verify Meta conversion tracking?; Logs shows what Crisper sent.

Meta's Conversions APIdevelopers.facebook.com receives events from a server, and Meta explains how it handles duplicate Pixel and Conversions API eventsdevelopers.facebook.com. Logs shows the request Crisper sent for each event, so you can see what Meta was given.

Where does an event open in Logs on a tablet or laptop?

On tablets and laptops, an event you pick in Logs now opens in a side panel on the right, beside the list, like Notifications. Phones keep the panel that slides up from the bottom, and a wide screen still shows the event beside the list on the page itself.

Open an event in the side panel

Where to find it: Dashboard → your website → Logs → select an event, on a screen at least 640 pixels wide

The panel shows where the event was sent and whether each platform got it, with the event's details below. The panel stays in place while its contents scroll, so Open log trace stays within reach on a short laptop screen.

When to use it: When you check a lead or purchase on a tablet or laptop and want the list in view while you read it.

Fig. 1Sample data · example.com. A picked event opens in the side panel beside the Logs list. Captured from the shipped component with example.com fixture data; illustrative, not a customer result.

See where saved key-event history starts

Where to find it: Dashboard → your website → Logs → Event → Key events → date picker

While saved key-event history covers less than 90 days, the date picker's footer says where it starts, such as Key-event history starts Nov 1. The date follows your Logs time zone, so a time zone behind UTC can show Oct 31. The line goes away once 90 days of history are saved. It names the day saved history began for every website, so a website added later has saved history only from its own start.

What does this not change?

Only where the event opens has changed: the details, delivery results and Open log trace are the same as before. The history line explains why the calendar stops there; it does not add older days.

Read next

How much saved key-event history you can read, each event's platform outcome, or download your Logs.

Which device and browser sent a conversion request?

The Visitor checked step in a conversion trace now shows device type and operating system alongside the browser and its version. Use those details to compare a request with the browser where you tested the form or checkout.

Read the device and browser rows

Where to find it: Dashboard → website → Logs → open an event's trace → Visitor checked. Device can show Mobile, Tablet or Desktop with the operating system; Browser includes its major version when available.

When to use it: When a form or checkout behaves differently on a phone, a desktop browser or an in-app browser.

Fig. 2Sample data · example.com. The Visitor checked step shows device type, operating system and browser version when the request includes enough information.

How are these details worked out?

The rows read the browser information included with the request. They show less when it does not contain a reliable version. A Macintosh request can read Mac or iPad because those devices can send the same browser information.

What should you avoid inferring?

This is a device hint, not an exact device identity or proof of a real person. Some automated requests have no device label. Keep the visitor verdict and the platform's reply separate from these rows.

What should you check next?

Read what bot labels mean, verify the conversion in Events Manager, or check the custom-site installation.

How do you export conversion logs to Excel or CSV?

You can now download your Logs as an Excel or CSV file. It holds the rows on your screen, with your dates, search and filters, ready to share with your developer or check in a spreadsheet.

How to download your Logs as Excel or CSV

Where to find it: Dashboard → choose a website → Logs → download icon

Set the dates, search and filters until the table shows the requests you want, then select the download icon next to the search box and choose Excel (.xlsx) or CSV. The menu shows how many rows the file will have. The file keeps the table’s rows and order, newest first unless you sorted it differently, and is named after the website and the date range.

When to use it: Share a set of requests with your developer, or compare a day’s purchases with your ad platform’s report.

Fig. 3Sample data on example.com, not customer traffic. The menu counts the rows the file will hold.

How to download a single request

Where to find it: Dashboard → choose a website → Logs → open a request → download icon

Open a request and use the download icon at the top right of its page. The same menu saves just that request, with the same columns as the full download.

When to use it: Send one purchase or lead to your developer or to support, in the same 18 columns as the full download.

Fig. 4Sample data on example.com. On a request’s page, the menu saves that one request.

What columns the Logs file includes

Each request is one row with 18 columns: the time in UTC and in the website’s time zone, the time zone, the event, the response status, the client, the request’s URL path, the domain, the trace and log IDs, the value in your store’s currency, the source and medium, the email, the phone, the click IDs, where the request was sent (each destination’s delivery state and HTTP status, or a note when delivery details aren’t available), and the original value and currency. The store-currency value is left blank when the amount can’t be shown in that currency; the original value and currency columns still hold it. The URL path column leaves out the query string. The Visitor label and bot score aren’t in the file. Cells that start like a formula are saved as plain text, so a spreadsheet won’t run them.

Fig. 5Sample data on example.com. The 18 columns of the file for two purchases, turned sideways to fit; in the file, each request is a row.

How the download picks its rows

The file is built in your browser from the table you’re viewing. Crisper doesn’t fetch anything extra, so the file matches the screen:

  1. It starts from the date range you set and the rows loaded for it.
  2. It keeps the rows that match your search (event, email, phone, source or click ID) and your filters, in the table’s order.
  3. It keeps the first 1,000 of those rows.
  4. It saves them as Excel or CSV, then confirms how many rows it saved, and says so when the file was capped at 1,000 or the date range is incomplete.

What the Logs download doesn’t include

It’s the rows you’re viewing, not every request on the website. Above 1,000 rows it keeps the first 1,000. When a date range is too large to load in full, the file holds only the loaded rows and Crisper tells you the range is incomplete; narrow the dates or filters to fit. The download icon is unavailable while Logs are loading or their delivery details are still being checked. The file can hold your customers’ emails and phone numbers, so store and share it as carefully as the dashboard.

Read next

How do you find your newest conversions in Logs?

When you are checking a recent lead or purchase, the newest requests matter first. Logs now shows the newest day as soon as it is ready and fills in older days in the background.

Start with the newest day

Where to find it: Dashboard → choose a website → Logs

Open Logs and start reading the newest day while the rest of your selected range loads. A progress message shows how many events have arrived so far. If an older day cannot load, the requests already loaded stay visible and the missing dates are named.

When to use it: When you want to inspect a recent request across a date range of several days.

Let the selected range finish loading

The first rows cover the newest day. Let the remaining days load before checking the full date range. Busy days can still show only their newest requests.

What happens when Meta refuses a conversion?

When Meta refuses a purchase or lead, it used to wait in Logs until someone re-sent it by hand. Crisper now finds those refusals every day and sends them again for you. Logs also stops showing Checking much sooner, so you can see what happened to a recent send within a few minutes.

How automatic re-send works

Where to find it: Dashboard → choose a website → Settings → Automatic re-send

Every day, Crisper re-sends Purchase and Lead events Meta refused in the last 6.5 days, up to 3 tries each. A daily limit is shared across websites, so a large number of refusals can take more than one day. It is on for every website. To stop it for one website, turn off Automatic re-send in that website's Settings and save. If most of a pixel's recent sends fail, Crisper pauses re-sends to that pixel until its Meta connection settings change.

When to use it: When you want refused Meta conversions sent again without checking Logs every day.

Fig. 6Sample data. Automatic re-send is on for every website; turn it off in that website’s Settings and save.

See a send's status sooner in Logs

Where to find it: Dashboard → choose a website → Logs

Logs shows Checking while a new event's sends are still being recorded. That now lasts about 3 minutes instead of 15, after which Logs shows whether each integration's send went out.

When to use it: When you have just sent a test purchase or lead.

Fig. 7Sample data. Checking now lasts about 3 minutes, then Logs shows whether each integration’s send went out.

What automatic re-send does not cover

It covers Meta Purchase and Lead events only, within Meta's 7-day limit for event age. A re-send succeeds only if the reason Meta refused the event has been fixed. Sends that failed for another reason, such as a timeout, other events, other platforms and sends that never went out still need Re-sync in Logs.

Read next

What else changed in Logs and re-sends?

Keep Submit Application logs up to date

Logs refreshes saved Submit Application events automatically, so the view stays up to date.

Give new conversions time to finish checking

When a new lead or purchase has no recorded send yet, Logs shows Checking for the first 3 minutes after the event and reads it again automatically. Re-sync isn't offered while it says Checking; if no send is recorded after that, the row shows Not sent.

As shipped on 30 October: When a new lead or purchase has no recorded send yet, Logs shows Checking and refreshes automatically. Re-sync waits through the 15-minute checking period. Since 5 November, the checking period is 3 minutes.

Purchase re-sends keep their currency

Re-sending a purchase that had no previous send now keeps its currency alongside its value.

Keep scanner requests out of your everyday Logs

Known scanner requests are hidden by default. A button above the table counts them, such as Show 3 scanner hits; select it to inspect them, and scanner requests are labelled Scanner rather than Person.

Phone numbers and international postcodes are formatted correctly on re-send

Meta re-sends now hash phone numbers in international format and keep the letters in non-US postcodes such as UK and Canadian ones, with US ZIP codes trimmed to five digits. TikTok re-sends keep the leading + on phone numbers.

Choose All logs from the date picker

The Logs date picker adds All logs for the available history, previews date ranges, and tells you when the oldest available day starts partway through the day.

More complete Meta delivery counts

Meta delivery totals can now pick up late confirmations for recent purchases and leads that earlier counts missed.

Open Logs from the final setup step

Open Logs for this site is now a button, both while setup waits for your first event and after one arrives.

Read Logs as event cards on a phone

Below tablet width, Logs shows one card per event with its time and delivery details, replacing the wide table.

A next step when Logs takes too long

A timed-out log lookup asks you to try fewer days or a single event.

Re-check delivery before re-sending an event

Logs checks Not sent results again, and a re-send to Meta or TikTok is skipped if a successful delivery is now recorded.

Logs day headings count leads as leads

A day heading in Logs now names key events in plain words, such as Today · 4 leads, instead of the raw event name, and leaves out the value when there is none to show.

Should you use Crisper to find, export and re-send conversions?

If Meta refuses your Lead or Purchase events and you want to see which ones, hand a day's purchases to your developer, or have the refused ones sent again without checking every morning, we recommend Crisper. Logs, the download and the daily re-send all work from the same record of requests. After setup, send a test lead, open Logs, and confirm its status moves from Checking to Delivered.

How do you see an event's outcome for each platform?

Open an event in Logs to read its recorded platform outcomes below the title. Use the newer and older arrows to compare nearby events without returning to the list.

Where can you find it?

Where to find it: Dashboard → website → Logs → open an event. When to use it: Check a test lead or failed send; the arrows sit beside Download.

Fig. 8Sample data · example.com. One recorded delivery, one failed send and newer/older controls.

How does it work, and what are its limits?

Platforms group the same delivery results as the list’s dots. Mixed results show delivered, failed and not-confirmed counts; failures link to Check Integrations. Arrows follow loaded events within the URL’s date, hour and event filters.

Arrows ignore in-page search text. Recorded delivery does not establish platform acceptance or attribution. An absent line can mean unknown delivery or nothing to send.

Verify Meta tracking, compare Logs with your CRM, or review automatic re-send.

How much saved key-event history can you read in Logs?

Crisper keeps saved key-event history for up to 90 days. It accumulates from 1 November 2026 UTC, or your website’s later coverage start, without backfilling removed days.

Where can you find it?

Where to find it: Dashboard → website → Logs → Event → Key events → date picker. When to use it: Revisit events on available earlier dates after full request details expire.

Fig. 9Sample data · example.com. Available dates begin on 1 November; history grows over time.

How does it work, and what are its limits?

Beyond the normal 10-day request window, Key events reads saved summaries: rows older than 10 days show a summary only. The calendar expands as history builds. MCP purchase and lead statistics can also read it; check the returned coverage.

Older rows have no full trace or re-send action. Other Logs views keep shorter windows. Missing or partial data is not zero events, and lead-drop detection still uses its recent 12-day window.

Choose key events, connect your AI assistant, or export the rows on screen.

What changed in this guide

  • 15 November 2026: Added where an event opens on tablets and laptops and the date picker's key-event history line. Added plainer day headings to What else changed in Logs.
  • 12 November 2026: Updated sections to how the product works today and corrected details that were wrong when they shipped. Retook the Logs download screenshot with all 18 columns.
  • 10 November 2026: Added per-platform event outcomes, newer/older navigation and the limits of accumulating saved key-event history.
  • 8 November 2026: Added a section on reading device and browser details in a conversion trace.

Sources

2 sources
  1. 1Conversions API↩
  2. 2handles duplicate Pixel and Conversions API events↩