Can Attribuly-Identified Anonymous Visitors Be Exported as a Separate Audience?

What are identified anonymous visitor leads?

Identified anonymous visitor leads are additional identified leads Attribuly can associate with previously anonymous visitor behavior. In plain language, these are visitors who were not directly captured by the store's normal signup forms or native marketing stack, but who can become usable for recovery, retargeting, or lifecycle activation through Attribuly-supported destinations.

These leads are valuable because they sit between anonymous traffic and reachable marketing profiles.

What is supported today?

Today, the main supported path is destination sync.

What is not supported today?

The following should not be promised as current self-serve product features:

• Direct export of identified anonymous visitor leads from the product UI.
• A self-serve CSV download of the identified anonymous visitor email list.
• A native "create standalone audience package" workflow inside the product.
• A general webhook that automatically sends every lead to any third-party server.
• A no-code Zapier push for all identified anonymous visitor leads.

These may be useful product directions, but they should be described as future or manual workflows unless they are already implemented.

Current activation workflow

The current workflow looks like this:

Anonymous Shopify visitors
  → Attribuly identifies additional leads through Attribuly identification
  → Leads become identified anonymous visitor leads
  → Leads sync to Klaviyo / cartsee / Omnisend
  → Or leads sync to Meta / Google audiences for remarketing
  → If needed, Attribuly manually exports emails from the database

This workflow gives marketers activation paths without requiring a self-serve standalone export.

When should you sync instead of export?

Most ecommerce teams should use syncs when the goal is immediate marketing activation.

If the goal is revenue recovery, syncing to a platform that can trigger a flow is usually more useful than downloading a file.

When would a manual export make sense?

A manual database export can make sense when the merchant needs something the current product does not expose directly, such as:

• A one-time CSV of identified anonymous visitor emails.
• A custom audience upload outside supported destinations.
• Internal BI analysis.
• Data QA with the Attribuly team.
• A migration or special activation workflow.

Because this is manual, it should be treated as an exception path, not the default user experience.

How to explain this to a customer

Use this answer:

> Attribuly's extra identified anonymous visitors correspond to identified anonymous visitor leads. Today, those leads cannot be directly exported from the product as a standalone audience package. They can be synced to email platforms like Klaviyo, cartsee, and Omnisend, or to ad platforms like Meta and Google for remarketing. If you urgently need the emails, our team can manually export them from the database. We also plan to support webhook-based delivery to third-party servers such as Zapier in the future.

This answer is precise, useful, and avoids overpromising.

How to structure the audience once exported manually

If Attribuly manually exports the leads, the audience file should include only fields needed for activation and governance.

Avoid exporting raw behavioral noise unless the merchant has a clear analytics use case.

What to expect from the future webhook workflow

The planned webhook direction would make this workflow more flexible. Instead of asking Attribuly to manually export a database file, merchants could send identified anonymous visitor leads to a third-party endpoint.

Example future workflow:

identified anonymous visitor lead created
  → webhook fires
  → Zapier or merchant server receives the lead
  → merchant routes it to CRM, ESP, CDP, warehouse, or custom system

Until that exists, the reliable paths are destination sync and manual export.