Skip to content

Commit fc2538d

Browse files
committed
Update Engage FAQs
1 parent d866d50 commit fc2538d

File tree

4 files changed

+24
-30
lines changed

4 files changed

+24
-30
lines changed

src/engage/journeys/faq-best-practices.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -65,37 +65,37 @@ Follow these best practices to test your journeys:
6565
- For early version journeys, scaffold Send to Destination steps without connecting to your production advertising or messaging destinations.
6666
- Verify individual users' progress through the Journey in the Profile explorer view.
6767

68-
## Frequently asked questions
68+
## FAQs
6969

70-
### How often do Journeys run?
70+
#### How often do Journeys run?
7171

7272
Journeys run in real-time, like real-time Audiences in Engage. This means that users will progress through Journeys as Segment receives new events.
7373

74-
### Can a user re-enter a Journey?
74+
#### Can a user re-enter a Journey?
7575

7676
Yes. Users must first exit a Journey, however, before entering it again. To learn more about Journey re-entry, read the [Journey re-entry section](/docs/engage/journeys/build-journey/#journey-re-entry) of the [Build a Journey](/docs/engage/journeys/build-journey/) page.
7777

78-
### What destinations does Journeys support?
78+
#### What destinations does Journeys support?
7979

8080
Journeys supports all Engage destinations, including Destination Functions. Read more in Send data to destinations.
8181

82-
### What are the reporting capabilities of Journeys?
82+
#### What are the reporting capabilities of Journeys?
8383

8484
When building a Journey, if you check **Use historical data**, you can see the estimated number of users in the initial cohort.
8585

8686
Once published, Journeys displays the number of users are in each step of the Journey at any given time.
8787

88-
### How are users sent to downstream destinations?
88+
#### How are users sent to downstream destinations?
8989

9090
The data type you send to a destination depends on whether the destination is an Event Destination or a List Destination.
9191

92-
### Which roles can access Journeys?
92+
#### Which roles can access Journeys?
9393
For Engage customers, users with either the Engage User or Engage Admin roles can create, edit, and delete journeys. Users with the Engage Read-only role are restricted to view-only access.
9494

95-
### Why am I seeing duplicate entry or exit events?
95+
#### Why am I seeing duplicate entry or exit events?
9696

9797
Journeys triggers audience or trait-related events for each email `external_id` on a profile. If a profile has two email addresses, you'll see two Audience Entered and two Audience Exited events for each Journey step. Journeys sends both email addresses to downstream destinations.
9898

99-
### How quickly do user profiles move through Journeys?
99+
#### How quickly do user profiles move through Journeys?
100100

101101
It may take up to five minutes for a user profile to enter each step of a Journey, including the entry condition. For Journey steps that reference a batch audience or SQL trait, Journeys processes user profiles at the same rate as the audience or trait computation. Visit the Engage docs to [learn more about compute times](/docs/engage/audiences/#understanding-compute-times).

src/engage/trait-activation/id-sync.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ With Customized setup, you can choose which identifiers you want to map downstre
6262
- You can only select a maximum of three identifiers with an `All` strategy.
6363

6464

65-
## Frequently asked questions
65+
## FAQs
6666

6767
#### What's the difference between Trait Enrichment and ID Sync?
6868

src/engage/trait-activation/trait-enrichment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ For best results with Trait Enrichment, Segment recommends:
125125
- Using Trait Enrichment with new audiences.
126126
- Using smaller audiences for real-time use cases, as data delivery is slower for large audiences.
127127

128-
## Frequently asked questions
128+
## FAQs
129129

130130
#### What's the difference between Trait Enrichment and ID Sync?
131131

src/engage/user-subscriptions/subscription-groups.md

Lines changed: 13 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -108,37 +108,34 @@ To set susbcription groups with the Identify call, you'll need to include a key-
108108
}
109109
```
110110

111-
## Frequently asked questions
111+
## FAQs
112+
113+
#### How many subscription groups can I have?
112114

113-
{% faq %}
114-
{% faqitem How many subscription groups can I have? %}
115115
Your Engage space includes up to 25 subscription groups.
116-
{% endfaqitem %}
117116

118-
{% faqitem Can I use subscription groups with templates I've already built? %}
117+
#### Can I use subscription groups with templates I've already built?
118+
119119
No. Templates you've previously created aren't compatible with subscription groups. To use subscription groups, you'll need to create new templates that include new unsubscribe and manage preference links.
120-
{% endfaqitem %}
121120

122-
{% faqitem What happens if I delete a subscription group? %}
121+
#### What happens if I delete a subscription group?
122+
123123
If you delete a subscription group, Engage will still maintain the preferences of the group's end users.
124-
{% endfaqitem %}
125124

126-
{% faqitem What subscription group events does the Engage Channels Source send? %}
127-
The [Engage Events Source](/docs/connections/sources/catalog/cloud-apps/engage-events/) tracks four subscription group events: `Email Unsubscribed`, `Email Group Unsubscribed`, `Channel Subscription Updated`, and `Group Subscription Updated`.
125+
#### What subscription group events does the Engage Channels Source send?
128126

129-
{% endfaqitem %}
127+
The [Engage Events Source](/docs/connections/sources/catalog/cloud-apps/engage-events/) tracks four subscription group events: `Email Unsubscribed`, `Email Group Unsubscribed`, `Channel Subscription Updated`, and `Group Subscription Updated`.
130128

131-
{% faqitem How can users opt back in if they've unsubscribed from all groups? %}
129+
#### How can users opt back in if they've unsubscribed from all groups?
132130
If a user unsubscribes from all of your subscription groups, they'll need to re-subscribe by explicitly opting back in to each group.
133-
{% endfaqitem %}
134131

135-
{% faqitem Do subscription preference links work in test emails? %}
132+
#### Do subscription preference links work in test emails?
133+
136134
Yes. Test emails include fully functional unsubscribe and subscription preference links. If a test email recipient unsubscribes using a test email, Segment updates that user's subscription state. <br><br>
137135

138136
Test emails temporarily override an email subscription state. This means that an unsubscribed email address can receive a test email but won't receive regular email campaigns from which they've unsubscribed.
139-
{% endfaqitem %}
140137

141-
{% faqitem Should I follow any conventions when naming a subscription group? %}
138+
#### Should I follow any conventions when naming a subscription group?
142139

143140
Yes. Keep the following table in mind when you name a subscription group:
144141

@@ -151,6 +148,3 @@ Yes. Keep the following table in mind when you name a subscription group:
151148
| Spaces in Group Names | Spaces aren't allowed at the beginning and/or end of the Group name |
152149
| Unsupported characters for Group Names | `!@#$%^&*()_+\-=\[\]{};':"\\|,.<>\/?` |
153150
| Unsupported accent characters for Group Names | `á, é, í, ó, ú, à, è, ì, ò, ù, ë, ï, ã` |
154-
{% endfaqitem %}
155-
156-
{% endfaq %}

0 commit comments

Comments
 (0)