- Customer Data
- Guide to using Respond
- Inbox Filtering
- Forms for Service
- Workflow States
- Bulk Changes
- Scheduled Replies
- Message Templates
- Finding Conversations
- Customer Profiles
- Grouped Messages
- Automation Rules
- Redact Messages
- Routing Customer Replies
- Chatbot User API
- Troubleshooting Respond
- Interact with Comments/Tweets
- Adobe Campaign
- Amazon S3
- Campaign Monitor
- Facebook Ads
- Google Display & Video 360 (DV360)
- Google Ads
- InMoment (formerly MaritzCX)
- Instagram Ads
- Offline Conversions [beta]
- Pinterest Ads
- Retention Science (ReSci)
- Salesforce Marketing Cloud
- Snapchat Ads
- Swift Digital
- TikTok Ads
- Twitter Ads
Connecting your Amazon S3 account with Lexer
When you connect your Amazon S3 account, you are allowing Lexer access to send data through Amazon S3 to your audience. This can easily be set-up in the Integrations panel. This allows you to send your customer data and segments to S3 for marketing campaigns through Activate.
Given Amazon S3 buckets all live near each other, moving data between buckets can often be quicker than sending it directly to a platform via an API. It's not always as easy, but the option to rapidly do this via S3 is handy.
Two key things required for set-up:
- Access Key ID
- Secret Access Key ID
You can find more details here: Amazon - managing access keys for IAM users
Benefits of an Amazon S3 integration
- Quick and easy access of data in your existing S3 Buckets.
- Activate more customer segments for marketing campaigns.
How do I integrate Amazon S3?
- Select the Amazon S3 tile
- Click Integrate External S3
- Enter the name of your S3 account
- Enter the Access Key ID and Secret Access Key
- Add the groups that will be allowed access to this integration
- Click Save Integration
Once you've connected your S3 account, contact Lexer Support to configure your Activation.
Privacy and security
Amazon S3 operates under SSL encrypted endpoints. You would have already configured this with your provider for encrypting these data with a suitable option for you. Lexer has established policies which define how information such as personally identifiable information or other sensitive client data is transferred between Lexer and third parties.
Buckets and Objects Access
You need to grant buckets and objects public access to Lexer through the Amazon S3 Console.
Detailed instructions can be found here: Working Amazon S3 Buckets
Permissions and Identity Access Management (IAM) Policies
We require permission to access all folders and files in the S3 bucket that contains your customer data. You will first need to create IAM policies that provides Lexer the permission to access the S3 buckets. Detailed instructions can be found here:
Amazon S3 creates buckets in a Region you specify. For your integration with Lexer, this is especially important to adhere to regulatory requirements across different regions. Data will only be accessed entirely within the hub. It will not be accessible from other hubs (unless there is an allowed crossover of data usage/access between hubs).
Once integrated, the data will undergo a QA and testing process by the Lexer team. We will be in contact with your team throughout the process to ensure a seamless delivery.