Skip to content

Commit 2265a67

Browse files
authored
Merge pull request #6123 from segmentio/courtneyga-patch-18
Added hyperlink for sending data to destinations via journey's
2 parents 7f42b64 + b08d323 commit 2265a67

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Yes. Users must first exit a Journey, however, before entering it again. To lear
7777

7878
#### What destinations does Journeys support?
7979

80-
Journeys supports all Engage destinations, including Destination Functions. Read more in Send data to destinations.
80+
Journeys supports all Engage destinations, including Destination Functions. Read more in [Send data to destinations](/docs/engage/journeys/send-data/) .
8181

8282
#### What are the reporting capabilities of Journeys?
8383

@@ -98,4 +98,4 @@ Journeys triggers audience or trait-related events for each email `external_id`
9898

9999
#### How quickly do user profiles move through Journeys?
100100

101-
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).
101+
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).

0 commit comments

Comments
 (0)