Adds a tutorial for automated messages

[iAmWillShepherd]

Addresses the task in Asana to draft a tutorial for event-triggered notifications by adding instructions for using automated messages.

[jfishman1]

IMHO, the main purpose of tutorials is to walk the person through start to finish and get to the "Aha" moment. They shouldn't need to contact Support or ask for help, the Tutorial should guide them through it leaving no room for interpretation or error.

When following the ReadMe, I don't see the point of calling this a tutorial, might as well just point to the Automated messages guide

I'm not sure if this is going to be 1 of 3 tutorials for Event Triggered Notifications, but the asana ticket outlines 3 ways to do "ETNs".

[iAmWillShepherd]

@jfishman1

IMHO, the main purpose of tutorials is to walk the person through start to finish and get to the "Aha" moment. They shouldn't need to contact Support or ask for help, the Tutorial should guide them through it leaving no room for interpretation or error.

Can you be specific on what you think is missing or which steps leave room for interpretation?

When following the ReadMe, I don't see the point of calling this a tutorial, might as well just point to the Automated messages guide

Maybe we have differing ideas of what a tutorial is—my definition: a transferral of knowledge through a set of instructions to accomplish a specific task; I think what I have here satisfies that definition. Perhaps some guidance on what you mean will be helpful?

I'm not sure if this is going to be 1 of 3 tutorials for Event-Triggered Notifications, but the asana ticket outlines 3 ways to do "ETNs".

This is one of three. PRs should be tight in scope. If those other sections weren't independent, I would've added them in this PR. See PR #2 to track work for the notification API.

[jfishman1]

@iAmWillShepherd I agree with your definition of tutorial, but IMHO this is not a transfer of knowledge on how to setup a specific task of event triggered notifications, it is a less detailed guide on how to setup automated messages.

Approaching this as someone who doesn't understand OneSignal and wants to setup "event" triggered notifications, it's not clear to me how to achieve that.

What I think you are missing:

1. Define the "event"

The customer needs to understand what exactly the "event" is and how to get that data into OneSignal.

I think you should start with a hypothetical event (user did or didn't finish a flow in the app/site) and build the tutorial around that.

I would start with data tags to explain getting the "event" into OneSignal part.

• How to capture events with data tags or what that would look like
• How do I use data tags to capture the event?
• What types of data tags should I use?
• What options do I have?
• How should I structure them?
• What are some best practices based on different events?

2. How to group users based on the "event"
   Now that tags are added, how do I know which users have them?
   What if the event can occur multiple times? How do I structure the segment so the user flows in and out each time they perform the event?

3. Then setup the automated message

Based on your current guide:
1 - Starting with Automated Message using "Subscribed Users". It doesn't explain why to use that segment. I don't think it should use that segment since it is not based on an "event".
How does the automated message work for events?
How often does it send to the user?
How quickly does it send to the user?
Why in step 7: "check if the user returns to the app delivery option"

• explanation of what the automated message delivery schedule options are and how they work

2 - Templates, says "dynamically generate the content of push notifications and emails" but how or why would I do that? What are best practices?

• explanation of how to use tags for personalized templates

3 - "Inspecting data tags" doesn't show how the data tags look in the dashboard, just how to get them. If a marketer needs to setup the segment, how do they know what they look like or what to do?

4 - Segment shows the "Create Segment" step but doesn't show the data tag filter being used with a data tags set in step 3
Customer may not know what the tags look like on that page or how to setup a segment with them.
If I am a marketer, how do I setup a segment with data tags?

It might be best to record yourself going through, end-to-end, how to setup event triggered notifications as reference.

[iAmWillShepherd]

@jfishman1, great feedback! I'll get to work on revisions.

[iAmWillShepherd]

@jfishman1 I've made some refinements to touch on some of the points you listed. I'm currently trying to organize the doc, but I'm unsure of the best order to present some of the concepts. Could you advise on this?

Fwiw, this draft is still incomplete; I'm mainly interested if I'm now on the right track.

[jmadler]

I suggest swapping this and the next paragraph as it forms a more direct line of increasing depth of subject matter coverage throughout the document. i.e. pyramid-shaped

[jmadler]

Same here -- sum up the section with a bit on how the template will be used.

[jmadler]

Maybe I'm missing something, but this doesn't seem like three distinct techniques, this seems like:
"Automating the Grouping of Users into Segments", "Tagging through the ... API", "Tagging in the ... SDK".

In other words, segments seems like they stand out in this set, which suggests that this isn't a MECE list. Is it a list of steps with options? Give it some thought.