1. Home
  2. Knowledge Base
  3. Thrive Automator
  4. Managing Automations
  5. What Type of Data Do Thrive Automator Triggers and Actions Use?
  1. Home
  2. Knowledge Base
  3. Developer Documentation
  4. What Type of Data Do Thrive Automator Triggers and Actions Use?

What Type of Data Do Thrive Automator Triggers and Actions Use?

In Thrive Automator, each trigger and action uses one or more sets of data. We have described all of the available actions, triggers, and filters that can be found in Thrive Automator in this article.

This one is dedicated to explaining what type of data each of the triggers and actions uses/captures when utilised in an automation.

For example, when using a WordPress trigger, such as “User logs into account”, you are creating an automation that starts whenever a user logs into their account through any form on your site. The data captured by this trigger is “User data”, and it contains parameters such as the user ID, email, WordPress role, username, etc.

Here are all of the available actions and start triggers, alongside the data they are capturing:

WordPress Account Start Triggers

Name

Captured Data (with examples)

User logs into account

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

User logs out of account

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Password reset link sent

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

User resets password

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

User creates new account

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

User profile updated

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Thrive Apprentice Start Triggers

Name

Captured Data (with examples)

Content is unlocked for a specific user

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Unlock Content Data (the type of content that is being unlocked – lessons/modules etc).

  • Product Data (for example: product ID, product name).

User makes progress in an Apprentice course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Course Data (for example: course title, topic, author).

User enrolls in a bundle (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Bundle Data (for example: bundle title).

User enrolls in a course (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Course Data (for example: course title, topic, author).

User completes all free lessons in a premium course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Course Data (for example: course title, topic, author)

User completes a lesson in a course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Lesson Data (for example: lesson title, type/module title, type).

User completes a module in a course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Lesson Data (for example: lesson title, type/module title, type).

User receives access to a product

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Product Data (for example: product ID, product name).

User purchases a Thrive Apprentice bundle (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Order Data (for example: product name, access type, payment date)

User purchases a Thrive Apprentice course (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Order Data (for example: product name, access type, payment date)

User makes a Thrive Apprentice purchase

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Order Data (for example: product name, access type, payment date)

User tries to access a restricted course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Lesson Data (for example: lesson title, type/module title, type).

User starts a course

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Course Data (for example: course title, topic, author).

User starts a lesson

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Lesson Data (for example: lesson title, type/module title, type).

User starts a module

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Module Data (for example: module title).

Thrive Ovation Start Triggers

User leaves a testimonial

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

  • Testimonial Data (for example: testimonial author, author role, author image, testimonial content)

Thrive Quiz Builder Start Triggers

Name

Captured Data (with examples)

User completes quiz

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • Quiz Data (for example: quiz title. type).

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

Thrive Ultimatum Start Triggers

User triggers Ultimatum evergreen campaign

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

  • Countdown Data (for example: campaign name, campaign type, campaign start date, etc.).

Thrive Architect Start Triggers

Form Submit

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

WooCommerce Start Triggers

Note: WooCommerce Start triggers will only work if you have set up WooCommerce on your site.

Name

Captured Data (with examples)

WooCommerce order completed

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • WooCommerce Order Data (for example: order number, customer ID, address details).

WooCommerce order refunded

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • WooCommerce Order Data (for example: order number, customer ID, address details).

WooCommerce order status change

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • WooCommerce Order Data (for example: order number, customer ID, address details).

WooCommerce product purchased

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • WooCommerce Product Data (for example: product name, product type, product price).

WooCommerce product refunded

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

  • WooCommerce Product Data (for example: product name, product type, product price).

Actions

Name

Captured Data (with examples)

Enroll user in course (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Remove user from course (deprecated)

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Grant access to product

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Remove access from product

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Unlock content for specific user

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

Add user in autoresponder

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

or

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

Tag user in autoresponder

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

or

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields)

Start an Ultimatum Campaign

  • User Data (for example: user ID, username, WordPress user role, email, registration date).

or

  • Lead Data (for example: name, email, data inserted in the “Textarea”/”Checkbox”/”URL” fields, data chosen in the “Checkbox”/”Select”/”Dropdown” fields).

These are the actions and triggers that are available in Thrive Automator, as well as the data they are capturing.

As for the Thrive Automator filters go, they are capturing singular sets of data, represented by the parameter that you’re actually using as a filter (WordPress user ID, registration date, etc ).

I hope this article was useful to you. Don’t forget to also check this one out, in case you want to see the list with all the available actions, triggers and filters, as well as their description.

For more information regarding Thrive Automator, be sure to check out these resources:

Was this article helpful?
Yes No

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
>