ข้ามไปยังเนื้อหา

Trigger-based entry

เนื้อหานี้ยังไม่มีในภาษาของคุณ

A Trigger-based entry starts the journey when a user performs a specific event (i.e., takes a specific action).

To set up a Trigger-based entry, locate the entry element on the canvas and select the Event that will serve as the trigger.

For more information on how to configure events, see the Events documentation.

If the selected Event has attributes, you can narrow the entry conditions using those attributes. Click Add condition when editing the element, then choose an attribute from the drop-down list and define its operator and value.

Define who enters the campaign

Anchor link to

When setting up a Trigger-based entry in a Pushwoosh Journey, you can define which user(s) should enter the journey when a specific event occurs.

Use the “Who enters the campaign?” dropdown to choose between the two available modes:

Users who perform the event (default)

Anchor link to

The user who triggers the event is the one who enters the journey.

Example
A user completes a purchase (CheckoutSuccess event). That same user (e.g., User ID: 123) enters a post-purchase journey that includes a thank-you message, product recommendations, or a satisfaction survey.

Select users who perform the event

Users from an event attribute

Anchor link to

Instead of enrolling the user who triggered the event, you can pass one or more User IDs in a custom event attribute. The users listed in that attribute will enter the journey.

For this, select Users from an event attribute and choose an attribute key (e.g., recipient_ids, target_user_id). This key should match your event payload structure.

Select users from an event attribute

Example payload (single user)
Anchor link to
{
"application": "XXXXX-XXXXX",
"event": "invitation",
"attributes": {
"targetId": 321
},
"userId": 123
}

User 321 (from targetId) enters the journey.

Example payload (multiple users)
Anchor link to

If you provide multiple user IDs, use a JSON array of strings.

{
"application": "XXXXX-XXXXX",
"event": "invitation",
"attributes": {
"targetIds": [1,2,3,4]
},
"userId": 123
}

Users 1, 2, 3, and 4 will enter the journey.

Comment notifications

When someone comments on a user’s post, the post owner is notified.

Example: A comment event includes the post owner’s ID in a target_user_id attribute. That user enters a journey to receive the notification.

Referral programs

When a referred user signs up or makes a purchase, the person who referred them is added to the journey.

Example: User 123 triggers the event, and the referrer 456 (from the referrer_id attribute) enters a reward campaign.

Gift purchases

When a user purchases a gift, the recipient is added to a journey using the recipient_user_id from the event payload.

Example: User 123 buys a gift for user 456, who then receives a notification, onboarding flow, or thank-you message.

Set entry availability

Anchor link to

Control when users can enter a journey via a trigger-based entry. You have two options:

  • Allow entry at any time: Users can enter the journey whenever the trigger event occurs.

  • Limit entry to a specific period: Users can only enter the journey if the trigger event happens within the selected date range.

    When limiting entry, select the start date, end date, and the timezone. The entry window begins at 00:00 on the start date and ends at 23:59 on the end date, based on the chosen timezone.

Set entry availability

Once you’ve configured the entry element, click Apply to save the changes.