Skip to main content
I am running into a Merge Field/Handlebar/Data Feed issue that I can't figure out. I have chatted with Iterable support and I haven't gotten back a solution. I am hoping the community can help me solve it.

I have created a workflow that reminds people to service their vehicle at exactly 6 months.
Scheduled Reoccurring list of our customers who have a Serviced Vehicle event, match query until I have the perfect 6 month customer, and send them an email. In the email I have to handle bar the recipient their Make and Model of their vehicle. For example: "Hey Adam your Honda Civic is due for service."

The Service Vehicle event with the customers Make and Model is an event, so it is not in the user profile, and in my situation it is not the triggering event of my workflow.



To supply the Make Model I created a Data Feed that pulls the last 200 user events from the Iterable API. Thanks to @Chris Kaundart and his data feed presentation video. My Data Feed alias is "Iterable_Events".

The Data Feed is an event array.


I can't hard code [[Iterable_Events.events.[11].dataFields.vehicle.model_name]] because if my example user has another event of any kind then [11] is inaccurate. Additionally, a users Serviced Vehicle event could be 0-199.

I have also tried
[[#each Iterable_Events.events]]
[[dataFields.vehicle.model_name]]
[[/each]]

but because users have more than one Serviced Vehicle event I get back Tucson and Civic for the Model Name.

Is there anyway to Handlebar in just my most recent Serviced Vehicle Model Name? Is there a better way to accomplish my goal?
Hi Kevin! Thanks for writing in. We have responded to your support ticket with some follow up information. You may need to utilize workflows triggered off the "Serviced Vehicle" event to add a field containing the most recent Model name onto the profile!
Hello Rachel, The suggestion is:
1. Trigger a workflow from your event named "Serviced Vehicles"
2. Then use a change contact node https://support.iterable.com/hc/en-us/articles/205674425-Workflow-Actions-#change-contact-field
3. And write that field to the user's profile {"newfield":""}
4. Then pull the field from the user's profile into your template

Essentially, you are saying to create a separate workflow, its only job is to trigger my event "Serviced Vehicle" and write the Make Model info into new field on the user's profile.

I see how this is a solution going forwards because in 6 months from now I will have users with the data in their user fields. How do I address the situation from now to 6 months? Am I misunderstanding something?
Hi Kevin,
You are correct that the presented solution will work going forwards to at least 6 months from now. More details should have been provided in your support ticket!

Reply


Terms & ConditionsCookie settings