fleetdm / fleet

Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center)
https://fleetdm.com
Other
3k stars 416 forks source link

Request: Track website activity on the SalesForce contact page #21694

Open Drew-P-drawers opened 1 month ago

Drew-P-drawers commented 1 month ago

Goal:

As a marketer or a sales rep, it would be great to see website activity linked to a contact in SalesForce if they've registered on the website so that we can see what actions they've taken on the website/ensure we're not sending information they're already privy to.

For all contacts that have done a "Website - Sign up"

Sampfluger88 commented 1 month ago

@Drew-P-drawers, Let's get together and create a list of the events you want to track for a particular contact.

eashaw commented 2 weeks ago

I looked into how we could do this with segment, and I'm less confident that that is the best way to do this. The two issues I see with doing this with Semgent are a required intermediary step and mapping the information we want to send to record fields.

The page view event in Segment does send the User ID of logged-in users when they visit pages, but we can't send other information with those events. An intermediary step using "Segment functions" would be required to add the information required to update SF records to page view events for logged-in users. We would also need to use a separate Segment function to add information to Salesforce records because Segment's native Salesforce destination does not support appending information when updating records.

I think we should instead use the Fleet website to do this, here is my proposal:

@Sampfluger88, what do you think about storing information about a contact's website activity in a separate SF object?

Sampfluger88 commented 2 weeks ago

Let's test with a new object, or an existing one, but I doubt that we can find one that would be specific enough.

eashaw commented 2 weeks ago

Feedback from @mikermcneil on the proposal above:

  1. Create a read-only custom object in SF, add it to a lightning page with test data to show how it looks and bring to design review (i.e. build out empty Salesforce first)
  2. Then if that looks good, we do the work to feed in the data
  3. Then Drew can see it all and then once he has a hypothesis about a psystage automation or any automation he wants to do from exploring that data, he makes a user story about what he wants to happen. (And that way we're not doing a bunch of salesforce workflows or external system thingies which won't even feed the resulting changes from automations back into the fleetdm.com database, which could mean e.g inconsistent psystage which would mean delivering the wrong emails, or worse)
Drew-P-drawers commented 5 days ago

Just leaving a note for @Drew-P-drawers to ask @Sampfluger88 about the progress of this during digital experience standup.