Dynamic Yield
Overview
Dynamic Yield enables website personalization and website A/B content testing. You can send data from Simon to Dynamic Yield via S3 using the steps below.
Action Type
Action | Function | Connected Flows | One-time | Triggered | Stream | Recurring | Journeys |
---|---|---|---|---|---|---|---|
Send file to Dynamic Yield via S3 | Send a file of your chosen fields and attributes to a Dynamic Yield path set up for Simon use. | ❌ | ✅ | ✅ | ❌ | ✅ | ✅ |
Authentication
To authenticate Dynamic Yield so you can use our integration from flows and journeys, you need to work with your account manager. At a high level, the process works like this:
- Let your account manager know you want to use Dynamic Yield from Simon, then give them these two items:
- a list of the fields and attributes you want to send
- the .csv of your attribute mapping
- Our team works with Dynamic Yield to set up a specific folder path for Simon to send data to then performs a test send. We'll let you know when the authentication is complete and provide you with the folder name to use below.
Use the action
Once your account is authenticated, add the Dynamic Yield action to a one time, triggered, or recurring flow, or a Journey:
File Details
Dynamic Yield requires the full path and file name to drop the file, in this format. Copy and paste this Jinja snipped to include the data and time required by Dynamic Yield. [dynamic yield id]/upload_{{ now() | format_datetime('YY-MM-dd_00-00') }}/CRM_data.csv
Fields
Choose the fields you want to send, or select a recent action to use the same fields used previously. You can send over any contact properties that will exist on the contact profile in Dynamic Yield.
Order fields correctly
All fields entered must show up in this exact order shared with Dynamic Yield at the outset.
Hash values in email field (SHA-256) after converting to lowercase
Choose this if you want to to anonymize and deduplicate data. You must check this box before clicking OK if you want to use it.
Updated 10 months ago