How contacts are created in mParticle by Mention Me
The following rules will apply when sending the contact information to mParticle:
- If the customer does not exist on your mParticle instance, then a new contact will be created
- If the customer does exist on your mParticle instance, then the existing contact will be updated with only Mention Me specific fields
Customer consent
You can choose to capture customer opt-in consent as part of your Mention Me customer journey, and then these are sent directly to mParticle without the need to download CSV files.
If a customer consents to your newsletter either via the Mention Me referee journey or via a newsletter post-purchase overlay, the opt-in request will automatically be sent to mParticle.
The consent is tracked using the GDPR consent purpose based on the consent category you selected when you set up the integration.
There will be a consent event shown against the customer profile in mParticle that the customer has consented to opt-in to your newsletter
Note: A customer can also consent to receive your newsletter via other channels outside of Mention Me, so Mention Me is not the source of truth for all your consent
Customer profile attributes
The following customer information is created/updated on the mParticle platform and can be seen on the mParticle User Profile page.
The attributes will be grouped in the Mention Me section:
| mParticle User Attribute | Description | Example |
|---|---|---|
| share_link |
For referrer contacts only
|
https://demo.mention-me.com/m/ol/xz3uz-joel-mcfly |
| dashboard_link |
For referrer contacts only
|
https://demo.mention-me.com/d/2674816/9c34b0c2 |
| share_source | The name of the share method the referee came from | OPEN-LINK |
| referrals |
Total number of successful referrals a contact has made (successful referral is defined as when the referee has made their first purchase)
|
5 |
| total_shares |
The total number of shares a customer has done
|
10 |
| email_shares | This will be populated if the referral has been shared via this share type | 2 |
| facebook_shares | This will be populated if the referral has been shared via this share type | 2 |
| facebook_messenger_shares | This will be populated if the referral has been shared via this share type | 2 |
| name_sharing_shares | This will be populated if the referral has been shared via this share type | 1 |
| whatsapp_shares | This will be populated if the referral has been shared via this share type | 3 |
| nps_score | The NPS score submitted by the customer at post-purchase | 8 |
| propensity_to_refer |
Only sent if you are running a Mention Me Smart Experiment. This will either be: High - If customer has a high propensity to refer Low - If customer has a low propensity to refer |
High |
| ecr_activity |
The Extended Customer Revenue (ECR) activity segment of a customer. Possible values include:
|
Active |
| ecr_status |
The Extended Customer Revenue (ECR) status segment of a customer. Possible values include:
|
High |
| network_id | The Network ID is the unique identifier of the Network that your customer belongs to | N-5051-153480685 |
|
first_share_date |
The date when the referrer made their first share with a friend about your brand | 2024-06-03T16:19:08.000Z |
| first_referral_date | The date when the referrer first successfully introduced someone to your brand | 2024-06-03T16:19:08.000Z |
| ast_share_date | The last time the referrer shared with a friend about your brand | 2024-06-03T16:19:08.000Z |
| last_referral_date | The last time the referrer successfully introduced someone to your brand | 2024-06-03T16:19:08.000Z |
| ecr_12m_predicted |
The Predicted ECR segment of a customer in 12 months' time Possible values include:
|
High |
| referrer_engaged |
This will be set if the referrer has actively engaged with a referral offer and accepts the terms and conditions |
Yes |
