Skip to main content

Is there a way inSided to better understand who’s not only signed up, but is coming back?

I can see a registration date, last login, if and when they post, reply, like, but I don’t seem to see a way to identify whether they are coming back or not.

Is that last_visit in the exports and just not visible elsewhere in Control?

Hi, Scott. 

I’ve been told that last_visit in the export is the same as “last login” in control, just using another label. 

I’ve also found that last_activity does include someone’s visit… however, that doesn’t match the definition Insided gives me. (But validated against Google Analytics, a last_activity column is usually a pretty close match to unique visitors from GA. … additionally that column is an exact match of active users identified by visit (not login) via the Salesforce integration … so I would recommend that as their last activity, but it doesn’t match Insided’s definition)

 

I share your interest in tracking active users by returning visits. From my experience, the salesforce integration was the best path to this. The exports are going to give you most recent time stamp, but won’t let you see that the user visited today, yesterday, and 2 weeks ago. But the salesforce integration allows you to log each individual visit and then develop salesforce reports to get your clear picture there.

Without that integration, I’m not sure there’s a way to do it. The exports and the API data feeds always give you the most recent, and you need some kind of historical activity picture.  


Geez, that’s a gong show! At least we should be giving things the same label across the application. 

The Salesforce integration is pretty limited at this point and reliant on a matching email record. Since we don’t always have customers logging in with our application, that leaves a gap, and since a record isn’t created (as I understand) where there isn’t a matching record, then we also miss out on tracking those that aren’t customers.


Yep. Our IT team found a way to address some of that, but it took a bit of troubleshooting. 

They setup something that creates new Salesforce contacts with new records so that everything has a match. 

And we also did a mass import of the legacy community members who weren’t matching, then reset the integration to get to a ~100% match and a full picture of the data. 

If you want to have a call between your team and ours, I’m sure my colleagues would be up for talking through what we did. 

But it took a bit to get Salesforce matching “all” community records so we could extend our reporting capabilities beyond what’s offered out-of-the-box. 


Interesting. I have no IT or technical resources, so will have to hold off on that offer, but will keep in mind should things change.


Reply