β¨ Brij x Attentive SMS Integration
Effortless Consumer Data Sync for Smarter SMS Marketing Activation
π Overview
The Brij and Attentive integration enables brands to automatically sync consumer data captured through Brijβs on-product experiences directly into Attentive. This real-time sync allows for immediate marketing action, personalized messaging, and scalable list-building β with zero manual effort.
π£ Why it matters:
Brands using Brij + Attentive can convert product interactions into CRM-ready profiles β instantly.
Brij transmits data to Attentive when the following condition is met:
β A valid phone number is submitted and SMS Marketing Consent is explicitly set to true during registration.
π How to Retrieve Your Attentive API Key & Sign-up Unit
To complete the Brij integration setup, youβll need your Attentive API Key. Hereβs how to obtain it:
Step-by-Step:
- Log into Attentive
- Visit https://ui.attentivemobile.com and log in with your admin credentials.
- Navigate to the App Marketplace
- Locate Marketplace in the left-hand side navigation menu.
- Create a New App
- Click the + Create App button in the top-right corner of the Marketplace page.
- Enter App Details
- App Name: Enter an internal-facing name (e.g., Brij Integration)
- Contact Email: Enter your email address so Attentive can reach you about any technical issues
-
Configure Permissions In the Permissions section, set the following access levels:
- β Subscribers β Write
- β Custom Events β Write (recommended for future enhancements)
- β Custom Attributes β Write (recommended for future enhancements)
- All other APIs can be set to No Access
-
Generate and Save the Key
- Click Create. A pop-up modal will display your unique API key.
- Paste it into Brij when setting up your automation, in the authentication step
- β οΈ Important: For security, Attentive will not show this API key again. Store it in a secure password manager.
- Find your Sign-up Unit ID
- This can be found in the Sign-up Units tab of the Attentive platform in the ID column for any API sign-up method.
- A new Sign-up unit may need to be created if one does not already exist for Brij. Every integration needs it's own ID.
- You can contact their White Glove team (whiteglove@attentivemobile.com) or your Client Strategy Manager at Attentive to request a sign-up source ID.
- Your Attentive CSM will need details about Brij and the opt-in such as:
- Attributes about the opt-in (promotional, manual entry, etc.)
- A preview of your opt-in page with a legal, compliant disclaimer
- Your Attentive CSM will need details about Brij and the opt-in such as:
π For more detail, see Attentive's official documentation on creating custom apps.
βοΈ How the Integration Works
Step 1: Choose Integration
- Go to Automations in Brij and Create New
- Name your automation (e.g., Brij β Attentive Sync)
- Select Attentive from the list of integrations
β Supports multiple integrations per account
Step 2: Authenticate
- Use an existing authentication or add a new one:
- Method: apiKey
- Paste in your secure Attentive API key
- Label the integration (e.g., Attentive US)
π Your data remains secure. API keys are encrypted and access-controlled.
Step 3: Version
- Choose Version 1
- Review version release notes before activating
π Version control helps future-proof your automation setup
Step 4: Filter by Experience
- Apply to All Experiences, or select specific Experiences
- This ensures only relevant campaigns can trigger the sync
Step 5: Set the Trigger
- Enable: On Registration Submission
π Real time syncing:
As soon as a consumer registers, their data is on its way to Attentive.
Step 6: Final Configurations
- Enter your Attentive Sign-Up Source ID
- Optional settings:
- β Pause automation if errors go above a threshold (ex: 50)
- β
Notify team emails when failures occur
π§ Smart error handling ensures your data stays clean and campaigns keep running
π€ What Data Gets Sent?
Brij only transmits data to Attentive when the following condition is met:
β A valid phone number is submitted and SMS Marketing Consent is explicitly set to true during registration.
If this condition is met, Brij sends:
- Phone Number
- Email Marketing Consent (if exists)
- SMS Marketing Consent
π« If SMS Consent is not provided or is false, no data is transmitted to Attentive at all β including email, phone number, and any consent fields.
π Consent Scenarios & Data Matrix for Email Registration
| User Step | Profile Stage | Consent type | Consent Behavior | Sent to Attentive |
| Step 1 - Ask for Email | Email given | Implicit (no checkbox) | Subscribed w/ Single Opt-in | Nothing sent to Attentive yet at this point |
| Email given - Checkbox NOT checked β | Explicit (false) | Subscription NOT added (remains unchanged if already existed) | Nothing sent to Attentive yet at this point | |
| Email given - Checkbox checked β | Explicit (true) | Subscribed w/ Single Opt-in | Nothing sent to Attentive yet at this point | |
| Step 2 - Ask for Phone Number | Phone given - Checkbox NOT checked β | Explicit (false) | Subscription NOT added (remains unchanged if already existed) | Nothing sent to Attentive yet at this point |
| Phone given - Checkbox checked β | Explicit (true) | Subscribed w/ Single Opt-in | Email, Phone, email_consent: true , sms_consent: true | |
| Optional part of Step 2 - Ask for Purchase Details | Purchase details given (retail channel, serial #, receipt, etc.) | N/A | N/A | Not sent to Attentive yet - let us know if you need this! |
π‘ Pro Tip:
Customize consent prompts in your Brij registration flow to maximize opt-ins.
πΌ Business Benefits
π Real-time marketing readiness
Profiles are campaign-ready for rich customer journeys the moment they register
β± Time savings at scale
No CSV uploads, no delays β fully automated sync
π‘ Consent-first data compliance
Consent flags are synced only if explicitly opted in
β οΈ Current Limitations
| Item | Status |
| SMS Rebate Customer Consent | β Not yet |
| Purchase Data or Full Event Details | β Not yet |
| Event triggers supported | β Registration Submission (aka Registration Completion) only |
π Version 1 Release Notes
- β Attentive authentication via secure API
- β Brij Registration Submission (Completion) as primary trigger
- β Support for Email, Phone, Email Consent, SMS Consent during email registration events
- β Intelligent error thresholds + failure notifications
- β
Experience-level filtering for scoped automation