> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Omnisend

> Forward identity-resolved customer events and profiles to Omnisend to power email and SMS automation, abandoned cart recovery flows, and workflow triggers via the Omnisend API.

<Note>
  **Data direction:** This is a **destination** — Upstack sends event and conversion data **out** to this platform via server-side APIs.
</Note>

Omnisend is connected through **Upstack Flows**, the product that handles event delivery to marketing automation platforms. The key value: Upstack identifies visitors that Shopify and Omnisend's native integration miss — turning anonymous browse and cart abandonment sessions into actionable Omnisend contacts with email addresses attached. This means more abandoned cart workflows fire, more browse abandonment messages send, and you recover revenue that would otherwise be invisible.

## How It Works

When a visitor takes an action on your store, Upstack:

1. Captures the event through the Upstack Pixel and matches it to a known visitor profile using Upstack's identity resolution.
2. If the visitor is identified (email available), enriches the event with the contact's email and any other known properties.
3. Sends the event to Omnisend using your Omnisend API key as a trackable activity that can trigger workflows.
4. Optionally creates or updates the contact in Omnisend so it can be segmented and messaged.

The result: abandoned cart and browse abandonment workflows fire for visitors that Shopify's native tracking misses.

## Set Up Omnisend

Follow the onboarding guide for the full end-to-end setup, or jump to a specific step.

<CardGroup cols={2}>
  <Card title="Onboarding guide" icon="book" href="/guides/omnisend/complete-how-to-guide-for-onboarding-omnisend-in-upstack-data">
    Complete step-by-step walkthrough for connecting Omnisend to Upstack.
  </Card>

  <Card title="Configure destination" icon="sliders" href="/guides/omnisend/how-to-configure-omnisend-pixel-destination-in-upstack-data">
    Add and configure the Omnisend destination inside the Upstack dashboard.
  </Card>

  <Card title="Generate API key" icon="key" href="/guides/omnisend/how-to-generate-your-omnisend-api-key">
    Generate the Omnisend API key Upstack uses to sync events and contacts.
  </Card>
</CardGroup>

## FAQ

<AccordionGroup>
  <Accordion title="How is this different from Omnisend's native Shopify integration?">
    Omnisend's native Shopify integration only sees visitors that Shopify has identified — typically logged-in customers or shoppers who have entered an email at checkout. Upstack's identity resolution matches anonymous sessions to known customer profiles using cookies, click IDs, and cross-session behavioral data, then sends those events to Omnisend with the contact's email attached. This lets your abandoned cart and browse abandonment workflows fire for many more visitors.
  </Accordion>

  <Accordion title="Will I get duplicate events if I keep Omnisend's native Shopify integration?">
    Possibly. If both Upstack and Omnisend's native integration send the same event types, Omnisend may record both. The recommended approach is to disable the corresponding events in Omnisend's native integration for any event types Upstack is configured to send, and keep the native integration only for events you're not routing through Upstack.
  </Accordion>

  <Accordion title="What permissions does the Omnisend API key need?">
    The Omnisend API key must have permission to write events and contacts. Use a key with the minimum scope required — Upstack does not need account management or billing permissions. Step-by-step instructions are in [Generate API key](/guides/omnisend/how-to-generate-your-omnisend-api-key).
  </Accordion>

  <Accordion title="How long does it take for events to appear in Omnisend?">
    Once the destination is active, events typically appear in Omnisend within 5 minutes. You can verify by triggering a test action on your store (such as adding a product to cart) and checking the contact's activity feed in Omnisend.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Data Enrichment" icon="magnifying-glass-plus" href="/concepts/data-enrichment">
    How Upstack Enrichment improves visitor identification — the foundation of Flows recovery.
  </Card>

  <Card title="Identity Resolution" icon="fingerprint" href="/concepts/identity-resolution">
    How Upstack ID connects anonymous sessions to known customers with email addresses.
  </Card>

  <Card title="Klaviyo Destination" icon="envelope" href="/destinations/klaviyo">
    Sync events and contacts to Klaviyo using the same Upstack Flows pipeline.
  </Card>

  <Card title="Events Not Reaching Destination" icon="wrench" href="/troubleshooting/events-not-reaching-destination">
    End-to-end diagnostic guide when events aren't arriving at any destination.
  </Card>
</CardGroup>