Suggested Car Listings
In this example, a car broker wants to send a subscriber an email that includes a list of makes and models of cars that the subscriber might like based on the subscriber's stated preference.
The car broker creates an attribute for the subscriber to contain the subscriber's preference in car type. The broker populates the attribute with a survey.
The car broker also creates a data extension that contains multiple makes and models of cars for each of the short list of types that the subscribers could choose in the survey. The car broker creates a data relationship to associate the car_preference attribute on the subscriber to the type column in the data extension.
The subscriber table contains this data:
email_address | first_name | last_name | region | car_preference |
---|---|---|---|---|
aruiz@example.com | Angel | Ruiz | north | sedan |
johndoe@example.com | John | Doe | south | convertible |
janedoe@example.com | Jane | Doe | north | SUV |
The cars data extension contains this data:
type | make | model |
---|---|---|
Sedan | Company A | Sedan A |
Sedan | Company B | Sedan B |
Sedan | Company C | Sedan C |
Convertible | Company D | Convertible A |
Convertible | Company E | Convertible B |
SUV | Company F | SUV A |
SUV | Company D | SUV B |
SUV | Company G | SUV C |
SUV | Company H | SUV D |
The car broker includes this AMPscript block in the body of the email:
When the car broker sends the email, the application processes the code:
Company | Model |
---|---|
Company A | Sedan A |
Company B | Sedan B |
Company C | Sedan C |
Company | Model |
---|---|
Company D | Convertible A |
Company E | Convertible B |
Company | Model |
---|---|
Company F | SUV A |
Company D | SUV B |
Company G | SUV C |
Company H | SUV D |