![amazon pinpoint amazon pinpoint](https://d0.awsstatic.com/product-marketing/Pinpoint/Pinpoint-feature-Overview1_6-8-2017.png)
If we were working with a dynamic segment, we could also configure messages to send when particular events arise within our apps, such as a purchase. Schedules can either be one-off - delivering messages immediately or at a specified time - or they can be recurring on an hourly, daily, weekly, or monthly basis. Standard campaigns deliver messages under a single delivery schedule.
![amazon pinpoint amazon pinpoint](https://info.radar.io/hubfs/PINPOINT.png)
We have two forms of campaign to choose from: standard or A/B test. With an imported segment ready for use, and both the email and SMS channels enabled, we’re ready to setup our campaign. Also, avoid spaces after your commas! Campaigns Read the supported attributes carefully to avoid this - some of them only accept a limited set of values.
AMAZON PINPOINT CODE
Let’s import this file from S3 to serve as our campaign segment.īe prepared to bash your head against the console on this - Pinpoint’s developed a bad habit returning HTTP status 400 and error code null if it fails to import the CSV data. This means the size of dynamic segments can change over time.įollowing a set of supported attributes, I’ve created a short CSV file consisting of four endpoints: two email addresses, and one phone number. Provided with at least one base segment and a set of filters, Pinpoint regularly re-evaluates dynamic segments using the provided filters in order to retain only the relevant endpoints. Once uploaded, this segment cannot change.ĭynamic segments can either be derived from imported segments or directly from users of your applications. When you import a segment from S3, Pinpoint establishes the number of endpoints it contains. Pinpoint fetches these files from Amazon Simple Storage Service (S3), which stores files in directories called “buckets”. Imported segments - as the name suggests - derive from file. These segments come in two forms: dynamic and imported. We can either group customers into a single segment, or divide the group into several segments based on one or more filters. Pinpoint supports “segments”, which provide the endpoints for our campaigns. With a range of channels at our disposal, now we need to provide contact details (otherwise known as “endpoints”) in order to reach out to our customers. Under beta release since November 2018, we can hook up Lambda functions to Pinpoint, providing the code to transform and deliver messages however we like. With all Pinpoint’s supported channels covered, what do we do if we want to configure our own channels? Say we wanted campaigns to raise alerts within our own web application, how do we do this? The answer: AWS Lambda. Since I have neither a development kit nor an app to hand, the push notifications are out of scope for this demo. Setting up push notifications for any one of these providers will require their respective development kit, as well as an app to use these push notifications. Supporting Firebase Cloud Messaging (FCM), Apple Push Notification Service (APNs) for iOS, Baidu Cloud Push for mobile devices in China, and Amazon Device Messaging (ADM), we’re spoilt for choice. Last - but not least - we have push notifications. Pinpoint can be setup to receive “YES” / “NO” responses to these messages. Suppose we were to message our customers and ask whether or not they were satisfied with a recently purchased product. You can configure Pinpoint to receive as well as send messages - enabling two-way communication for further customer engagement. If you were looking to obtain a code for your campaign, you would typically request a short one for large-scale communication (keeping in mind that campaigns do not yet support voice messaging). Typically we would use promotional SMS, but if any of your messages were time sensitive (say, to notify of a failed payment, or provide a one-time password), then transactional would be preferable.įor the purposes of this demo, we do not require any codes. AWS will optimise the former for highest reliability, whilst optimising the latter for lowest cost. Notice we’re offered two default message types: transactional and promotional.