Using the Activity Log to see why my guests are not syncing

You got your integration up and running - congrats!

While we hope that each and every guest will sync over seamlessly, there's a chance that you'll run into some sync discrepancies. That's okay, and in most cases, there's a quick solve.

Whenever you notice that a particular guest isn't syncing to your third party tool, you can check out your integration's Activity Log to see why that guest didn't make it over.


The Basics: What is the Activity Log, and what will it show me?

The Activity Log can be found at the bottom right of most configurations. The exception here is your Salesforce integration. If you're noticing some sync discrepancies between Splash and Salesforce, check out: Performing a re-sync with the Salesforce Debugger

For all other integrations, we'll defer to the Activity Log. This log will display a "timestamp" of every real-time guest sync, every configuration edit, and every Splash event update. 

You can find the Activity Log at the bottom left of your configuration. 


To start, you'll need to grab an example of a guest within your Splash Guest List that did not sync over. Jot down their email address and their Splash Guest list status - you'll need these later on. 

Got that guest? Great. Let's begin!

  1. First, we'll start by heading over to your configuration. Is your guest's status set up to sync here? Keep in mind that Splash will only sync over guests if their statuses are mapped here.
  2. If this checks out, then we'll head down to the Activity Log located at the bottom right of your configuration. 
  3. Click to open the Activity log, use the field at the top to search for your guest's email address, then click "return." This will display an entry of each and every time Splash attempted to sync this guest from Splash to your integration. Each entry will have a date and timestamp that represents when the sync was triggered. Look for one that is closest to when your guest RSVPd via Splash.

    Keep in mind - You will not see an Activity Log timestamp for guest data that hasn't synced over yet if there is a delay in Splash's API queue. Hang tight, it'll post soon!

    We also suggest reviewing our API queue guidelines. It's possible that your team may have maxed out on your daily API call limit. For more information on this, check out: What will happen if my team reaches our daily API limit?

  4. From there, click on the blue text labeled "Show Details" to see the entire payload. You'll notice some familiar data in there - including your event title, the guest's details, and more.

  5. Towards the bottom of the payload, you might notice the word status. Picking this out will be the bread and butter of your investigation. Typically, this line will read "Status:200."

200 means that Splash successfully sent the data over to your system. Amazing!
However, you might see another message appear. If you're an Integrations Admin, you'll probably recognize the meaning of the code. This will give you an idea of what's going on and what you'll need to do to resolve. If you need a refresher, check out some resources from your third-party tech's Help Center! Here are a few of our favorites:

Marketo's API Error Code Documentation
Hubspot API Error Responses
Greenhouse Harvest API
Pardot Error Codes & Messaging

As always, if you have any questions or concerns, drop us a line and we'll be happy to help!



Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.