ePrivacy and GPDR Cookie Consent by Cookie Consent

Meiro Knowledge Base

Meiro Audience API

The API endpoint is developed to check if a customer entity belongs to a defined segment in Meiro Business Explorer. 

API returns 200 responses along with predefined attributes when the customer entity belongs to a defined segment. Attributes of the customer entity are not returned by default. 

Customers' attributes to be returned by the successful API call must be defined in the configuration of the WBS container (for safety reasons). Any customer entity attribute might be returned.

Warning: contact Meiro team/ administrator to set the attributes.


 Authentication is not required.


GET: https://cdp.{{CLIENT_INSTANCE_NAME}}.meiro.io/wbs?attribute=&value=&segment=



Data type


attribute (required)


ID of the attribute used for profile stitching,


ps_meiro_user_id Meiro user ID
ps_email_address Email address
etc depends on client's use case


value (required)


Value of defined profile stitching attribute,


29f3aec1-1111-4294-b940-019698f4ac25 Meiro user ID tracked from client website where Meiro SDK is deployed
john@doe.com email address example


segment (required)


The ID of the segment in Meiro Business Explorer segment builder where the presence of the customer entity should be checked.

Valid request example

GET: https://cdp.CLIENT_INSTANCE_NAME.meiro.io/wbs?attribute=ps_meiro_user_id&value=29f3aec1-1111-4294-b940-019698f4ac25&segment=42

Response examples


Customer entity belongs to a defined segment:

  "status": "ok",
  "returned_attributes": {
    "customer_entity_id": "0000000071e3908f5aaaf022aa842b45",
    "modified": "2000-01-01 00:00:00",
    "attribute_first_name": ["John"],
    "attribute_last_name": ["Doe"],
    "attribute_total_order_value": null

customer_entity_id (default)

Internal ID of customer entity.

modified (default) Timestamp of last update of customer entity's attributes.
Returned attributes



attribute_total_order_value must be defined specifically for the client's use case in the configuration of `WBS` container.

404 (Customer not in the segment)

The customer entity defined in the API call is known in the Meiro database but does not belong to the defined segment ID.

  "status": "error",
  "message": "customer not in segment"

404 (Customer not found)

There is no customer entity with a defined value of profile stitching attribute in the Meiro database.

  "status": "error",
  "message": "customer not found"

50x (Internal server error)

 Internal server error. Contact administrator.




Meiro Customer Data Platform (CDP) - How does it all work together

Learn from this article about:


Meiro Events

Meiro Integrations

Meiro Business Explorer


Learn more: About customer data platforms (CDP) from this article and Meiro blog.


Meiro Events

Meiro Events is built as the first layer of the CDP stack to collect customers’ data from websites and mobile applications

Meiro Events is treated as 1st party data, therefore is possible to collect more data than from 3rd party providers, for a longer time (up to 2 years). 

Although it is recommended to use Meiro Events for data collection, it is not a prerequisite for using Meiro products. 

Learn more: About Meiro Events from this documentation.


Meiro Integrations

In Meiro Integrations data can be collected from various data sources, processed and delivered to data destinations.

Usually, this work is performed by skilled data analysts that can easily clean and process available data to make the most use of it. 

Learn more: About Meiro Integrations from this documentation.


Meiro Business Explorer

Meiro Business Explorer, with its a user-friendly interface, allows browsing through the customers’ database, building segments, seeing individual customers profiles and reporting on data. Meiro Business Explorer is easy to use for even non-technical users. Segmented customers can be easily exported to the chosen data destination within clicks.

Between Meiro Integrations and Meiro Business Explorer data is stored in the data warehouse (either your choice or managed by us).

Learn more: About Meiro Business Explorer from this documentation





Identity stitching and how customer identity appears


Learn from this article about:


Data collection

Identity stitching

Browse through stitched customer data

How can I check my customer identity?

How long does it take to build a customer identity?

Who has control over customers’ identities?


Customer entities are defined through a process called identity stitching. There is no magic behind it but only one rule: if two events share the same identifier, they belong to the same customer entity. In the same time it is possible to define multiple identifiers that make customer profiles more accurate.

Data collection

First data is collected from various data sources (for example Meiro Events, Facebook) and it can be used for marketing automation tools, databases of customers like CRMs, or anything else. Collected data is processed within Meiro Integrations.

Learn more: About currently available connections please refer to this articleIf you do not see a source you need, please contact the Meiro team.


Identity stitching

Collected data is cleaned and stitched within Meiro Integrations. This is where the identity stitching is managed by the data analysts team. 

During this process, various customer “identifiers” are defined (for example email, phone number, cookie) and extracted from events. If two events share the same identifier (for example the same email), they are assigned to the same customer entity. After identity stitching, other attributes are computed to enrich customer profiles with as much information as possible.

Identity stitching can be fully customized during the implementation process.




Browse through stitched customer data 

Customer identity data collected and stitched within Meiro Integrations is delivered to Meiro Business Explorer where any user (including non IT, technical users) can easily browse through it, as well as:



How can I check the customers’ identity for each customer?

For each customer profile, it is possible to view an Identity Graph that will demonstrate how data has been stitched together. It is a simple color-coded graph showing what data and when has been connected.

Why would I like to know the identity graph?

It is possible to check out how various data is connected together, as well as inspect the quality of stitched data. It allows easy to spot any abnormalities possible to investigate further with analysts. 


Learn more: about identity stitching with Meiro here. 


How long does it take to build a customer identity?

It depends on each client, its data sources and the volume of the data. Usually, customer entities are calculated almost in real-time.  

Who has control over customers’ identity?

Each client is in full control of customers’ identity and can choose identifiers that will define customers. 

Customer identities are calculated by the Meiro algorithm managed and designed by our analysts' team. It is possible at any time to investigate further and check out the reasoning of it, as well as change it if needed due to the client’s specificity. 


What happens to the data if I decide to stop using Meiro?

All your data belongs to you which is backed up by Meiro Terms & Conditions.

This means that by design the right to access data ( 1st party customer data, metadata, processing scripts, and components configurations made for the project), free of charge, any time.

For on-premises instances, the client has full access to the data as all products are running on the client's infrastructure and can access the underlying databases at any time.

If Meiro CDP is managed by Meiro, it is possible to extract data easily using Meiro Integrations (please contact Meiro support if you need help). Meiro will provide processing scripts and components configurations in under 24 hours upon request.

Please contact the Meiro team.

For marketing teams

For marketing teams

5 cases of exclusion marketing. Why & how to do it right

Learn about:

5 cases of exclusion marketing

Summary and takeaways for various teams

You may ask yourself why you would exclude any customers from your segmentation. It seems that more segmented customers= better, right? 

First of all in the era of high level personalization, it is important that you segment only the right people to limit wasted effort. For example, you may have in mind a campaign with promotion code that is limited to a certain number of customers, therefore you want to be sure you have the right customers that you send it to. …..

Beside all you want to avoid customers that will not benefit from your campaigning efforts, or even worse that you can annoy.

There may also be serious security reasons that you wish to comply with, let's look at them closer below.

Also since Meiro CDP is connecting your data from various data sources, you simply know more about your customers, so you can segment precisely the audience you need. 

Targeting the right audience can increase your click rate up to 400%, and open rate to 200%, we checked this out. 


5 cases of exclusion marketing

Case 1
Do not annoy your current customers. Exclude customers that you know may be simply not interested in your campaign.

But wait how would you know it? Simple, first set up clear campaign objectives and define which customers may not be interested in it. 



1. You are preparing a campaign for a new cosmetic product targeted for women, you will be sending promotional messages with various tips on how to use the product.

Exclude male customers, as they will likely feel advertising is irrelevant to them.

2. You are planning a campaign on Facebook to encourage people to sign up for a newsletter managed in Mailchimp. 

While segmenting your audience and sending it further to Facebook, you may consider excluding customers that are already signed to the newsletter, so you do not waste your marketing efforts and do not annoy your customers with irrelevant ads. 

3. You are planning a special promotion webinar for your products, you wish to drive more sign ups. At the same time you do not want to bother customers that are already signed.

Exclude customers who already signed to your event. 


Case 2
Do not waste your marketing budget. Exclude your current customers and save money on your advertising.



You are planning a new campaign to drive more customers. Your budget is tight and you want to spend your marketing money wisely. 

Within a few clicks you can segment only the customers that did not buy your product (just visited the website or maybe abandon the shopping card). 

Pick the attribute connected to customers spending, for example, select customers with revenue higher than 0, therefore select customers with total revenue= 0. 

Another way of doing it is to exclude customers with revenue higher than 0, you can do it through the “not” function. 


Case 3
Do not worsen your relationship with the current customers. Drop out from your campaign customers that complained to your customer service team, disturbed your previous events or simply competitors.



Planning a new campaign but do not want to waste you marketing spending on customers that have an issue opened with the customer service team. You know it may not be productive, even more it may annoy your customers that are currently not happy with your service. They need special treatment, not an usual marketing campaign. 

Exclude customers that have issues unresolved within the customer service team. This can range from customers with unresolved complaints or unfulfilled product returns in an ecommerce business, or a customer with outstanding insurance payout for an insurance business.


Case 4
Stay secure and pii data compliant and exclude customers you do not have permission to contact or when you need to stay aligned with special regulations if those concerns you.



Would like to be sure that you are sending campaigns only to the customers that gave you contact permission. Permission can come through telemarketing/sms/email.

Exclude customers that did not agree on contact, or are not sure if they wish to be contacted.

Are you from a business that is limited by special regulations, let say you are selling alcohol therefore you can not advertise to customers below 18th years old? 

No problem. Simply segment customers that are within the age group that interests you.

Case 5
Save your budget & exclude channels with low- engagement.

Even when you have built an ideal customer segment that is hyper targeted, it is useful to get some insights on their engagement history in your chosen channel. For example, before activating a retargeting segment through programmatic you may find that part of your segment has very low engagement (click throughs) in programmatic ads. In this case, it might make sense to exclude this sub-segment from programmatic means and activate them in other channels with better affinity.



Sending campaigns to the channels that your segment does not engage much.

Check engagement level for various channels in the insights and choose the ones that your customers engage with the most. 




Summary and takeaways for various teams

Let’s begin with stating the most important point that super powers CDP give you and your marketing teams are mostly coming from unifying various data from multiple data sources, on top of it being possible to stitch together into complete customer profiles with unified taxonomy.

Thanks to those it is far much easier to be sure that you target the right customers, as you simply have a better picture of who they are. 

For campaign manager

Set up your campaign objectives and see how you can optimize campaigns in the best way, which groups you have to exclude and which you could/ should to optimize the results. 

You can always check out your attributes in the Data tab/ Attribute tab and check which data is available for your customers. 

It is possible to set attributes  within Meiro CDP for your customers that will make compliance with various security regulations, statutory regulations possible and simple. It will save your team's time and make it possible to set segments within a few clicks. Contact the Meiro team if you have further questions. 

For marketing teams

How to check for Facebook Conversion API results?

Facebook Conversions API is designed to create a direct and reliable connection between marketing data (such as website events and offline conversions) from Meiro’s server to Facebook. Meiro implements the integration of Facebook Conversions API so that you can push events such as purchases or leads to Facebook Ads Manager while maintaining user privacy.

To check the results of Facebook Conversion API events, simply follow these steps:


Step 1 Go to Business Facebook 
Step 2 Select business account
Step 3

Select All Tools > Events Manager


Screenshot 2021-10-08 at 3.55.20 PM.png

Step 4

Select Facebook Pixel 


Screenshot 2021-10-08 at 3.56.10 PM.png

Step 5

Select the date range you want to see the results

  • The date range is set by default on “Last 28 Days” 

Web events received through integration methods such as the Facebook pixel and Conversions API are displayed in two tabs: Pixel/Conversions API tab and the Aggregated Event Measurement tab

The Aggregated Event Measurement tab shows a subset of your total events, so these counts may be smaller than the Pixel/Conversions API tab


Learn more: Refer here for more information.

Step 6

Under the “Pixel/Conversions API” tab, look for “Browser · Server” under the “Connection Method. There is no reporting available for Aggregated Event Measurement at the moment.

  • The browser means results from Facebook Pixel
  • The server means results from Facebook Conversion API


  • Screenshot 2021-10-08 at 3.56.47 PM.png
Step 7

Hover the mouse over each date to check or export the data for offline usage.