Data Sources & API

What are data sources and how do they work?

Last updated

A data source is a table of your own data that Sendtric can read when an email is opened. Each row (or record) belongs to one person or item, and a unique identifier like a customer ID or email address tells Sendtric which row to use. Your personalized and rule-based images can then show values your email platform doesn't hold, such as loyalty points, a booking reference or the nearest store.

You'll find them under Data sources in the left sidebar of your dashboard.

Data sources are part of the Enterprise plan, and some data source features are also included on Power. See plans and pricing for details.

How it works

  1. You create a data source and choose where its data comes from.
  2. You add a value from it to a widget: a text layer in a personalized image, or a condition in a rule-based image.
  3. The widget's code carries each subscriber's identifier through your email platform's merge tag, for example customer_id={{customer_id}}.
  4. When the email is opened, Sendtric finds that subscriber's row and draws the value into the image.

Where your data can come from

SourceHow data gets inGood for
CSV UploadYou upload a file, then edit it in SendtricLists that change now and then
API: Send data to SendtricYour system pushes JSON records to a Sendtric endpointData that changes often, sent from your own code
API: Retrieve data from an APISendtric calls your API when an email is openedData that must always be current
Integrations (Zapier or n8n)A Zap or workflow pushes records to SendtricData in apps you already automate

Each one has its own guide:

Hosted and connected data

Hosted data is stored in Sendtric: CSV uploads, records you push with the API, and records from Zapier or n8n. Connected data stays in your system, and Sendtric asks your API for it each time it's needed. You'll see these two names again when you pick a data source in the image editor.

The unique identifier

Every data source has one identifier field, such as customer_id, email or order_number. Pick a value that:

  • exists for every subscriber in your email platform, so a merge tag can fill it in;
  • is unique, so one subscriber never matches someone else's row;
  • doesn't change, so old emails keep finding the right row.

For hosted data, matching ignores upper and lower case, so CUST_1001 and cust_1001 are the same record.

An internal ID like a customer number is usually a better identifier than an email address. Email addresses change, and an ID keeps personal details out of your image links.

How fresh is the data?

  • Records you push with the API, Zapier or n8n are usually available within about a minute.
  • Sendtric keeps a generated image for the Cache time you choose in the image editor (2 to 60 minutes). A subscriber who opens the email again within that time sees the same image.

If you're sending thousands of records at once, see how to send large amounts of data to a data source.

Related

Was this article helpful?

Click the image to zoom in. Drag or scroll to look around.