Skip to content

Reference

Here is a comprehensive list of all the actions on DoDays that trigger an interaction with ActiveCampaign and the outcome.

  1. Staff member starts the ActiveCampaign set up:

    • ActiveCampaign account is linked to DoDays account using the provided ActiveCampaign URL and Key taken in Settings => Developer.
    • Marketing tag is created on ActiveCampaign.
    • Booked tag is created on ActiveCampaign.
    • Venue tags are created for all venues on ActiveCampaign.
    • 40 student custom fields are created, supporting 10 students with 4 fields for name, dob, working towards and last stage awarded.
    • The 20 working towards and last stage awarded custom field options are created for all stages.
    • Webhook created to listen for a contact unsubscribing, this will then opt the customer out of marketing on DoDays.
    • All customers who are actively booked into a class will be created on your ActiveCampaign account as per point 2. below.
  2. Staff member books a student into a class; OR; Customer self-books one or multiple students onto a class:

    • Contact is created with name, email address and phone number if they don't already exist on ActiveCampaign.
    • Marketing tag is added to contact if they have opted in to marketing.
    • Booked tag is added to contact.
    • Venue tag is added to contact.
    • Student(s) are added to the contacts custom fields if they don't already exist.
  3. Staff member removes a student from a class:

    • Booked tag is removed from contact on ActiveCampaign if the customer (and all their students) no longer attends a class.
    • Student is removed from contacts custom fields if they no longer attend a class.
    • Venue tag is removed from contact if the customer no longer attends this venue.
  4. Staff member updates a classes venue:

    • Old venue tag is removed from all contacts attending the class if they no longer attend this venue.
    • New venue tag is added to all contacts attending the class.
  5. Staff member updates a customers name, email address or telephone number; OR; Customer updates their own name, email address or telephone number:

    • Contact details are updated if they exist on ActiveCampaign.
  6. Staff member updates a students name or date of birth; OR; Customer updates one of their students name or date of birth:

    • Student custom fields are updated on contact if they exist on ActiveCampaign and the student exists on contact.
  7. Marketing consent is toggled by customer:

    • Marketing tag is added to contact if they exist on ActiveCampaign and are opting in to marketing.
    • Marketing tag is removed from contact if they exist on ActiveCampaign and are opting out of marketing.
  8. Stage is changed on student:

    • Working towards custom field is changed on contact if they exist on ActiveCampaign and student exists on contact.
  9. Stage is removed from student:

    • Working towards custom field is removed from contact if they exist on ActiveCampaign and student exists on contact.
  10. Stage is awarded to student:

  • Last stage awarded custom field is changed on contact if they exist on ActiveCampaign and student exists on contact.
  1. New venue is created:
  • Venue tag is created on ActiveCampaign.
  1. Existing venue name is updated:
  • Venue tag is updated on ActiveCampaign.
  1. New stage is created:
  • Stage option is created for all student working towards and last stage awarded custom fields.
  1. Existing stage name is updated:
  • Stage option is created for all student working towards and last stage awarded custom fields. See point 2. of ActiveCampaign API Limitations below for further details on why we can't just update the existing Custom Field Option and what implications this has on your integration with ActiveCampaign.
  1. Contact purging:
  • Nightly, DoDays will search for any customers who are present on your ActiveCampaign account but no longer actively booked into a class and remove them.

ActiveCampaign API Limitations

There are a few limitations with the ActiveCampaign API we need to be aware of:

  1. There is no way of creating Custom Groups to organise your Custom Fields over the ActiveCampaign API.

    Therefore, the 40 student fields we create will fall into the General Details group on ActiveCampaign.

    You can however create Custom Groups on ActiveCampaign yourself and update the fields to sit under these groups. For instance you can create a Student 1 group and move all your student 1 fields onto this group.

  2. The ActiveCampaign API doesn't allow you to update Custom Field Options.

    Therefore, if a particular stage has been added to a students working towards or last stage awarded fields on ActiveCampaign, and this stage name is updated on DoDays, the name of this stage won't be updated for these students on ActiveCampaign.

    Instead, a new option will be created for the working towards or last stage awarded fields on ActiveCampaign, and in the future this new option will be used on ActiveCampaign when adding the updated stage to a student on DoDays.

  3. ActiveCampaign doesn't offer a webhook event for contacts being removed from ActiveCampaign.

    Therefore, DoDays will potentially hold stale data and incorrectly think a contact exists on ActiveCampaign if they are deleted from the ActiveCampaign platform.

    The only solution for this is to never remove contacts from ActiveCampaign and let DoDays manage this for you.