Enhancement: Echo to D.T. | Distinguish between different social media brands in one permission set / one D.T. instance

[JCooper1979]

Enhancement: Echo to D.T. | Distinguish between different social media brands in one permission set / one D.T. instance

[kodinkat]

@kodinkat I could try to send you screenshots. I could also hop on zoom and try to show you.

@JCooper1979 Please fire across some screenshots of your current Echo setup and we can take it from there.. Thanks.. :)

[kodinkat]

Thanks @JCooper1979 Will aim to circle back to this and let you know what I find....

[kodinkat]

Hey @JCooper1979,

I'm just bringing myself up to speed with regards to this - Would concatenating the existing Echo source tag, with a conversation referrer be suitable for your needs?

For example, based on the proposed, a contact's source would be as follows: Echo - GodLife Community

From there, you'd be able to query the respective sources using the Sources Chart within metrics.

How does this sound?

[corsacca]

@kodinkat could the conversation referrer be but into the campaigns field?

[JCooper1979]

@kodinkat thanks for your reply. I am not sure. Would we be able to send multiple sources from Echo to one Disciple.Tools instance and distinguish between them using the conversation referrers? In other words would I be able to choose more than one conversation referrer per DT instance? I would need to see this in action to know if this is a fix.

[kodinkat]

@kodinkat could the conversation referrer be but into the campaigns field?

Ah, yes; that would make more sense! So, keep source field as is, with Echo and place the respective conversation referrer into campaigns field on contact record creation... Yep, that works! :)

[kodinkat]

@kodinkat thanks for your reply. I am not sure. Would we be able to send multiple sources from Echo to one Disciple.Tools instance and distinguish between them using the conversation referrers? In other words would I be able to choose more than one conversation referrer per DT instance? I would need to see this in action to know if this is a fix.

Hey @JCooper1979 currently as it stands within the Echo plugin, you do have the option of pulling-in / converting conversations from different referrers within the same D.T instance.

Therefore, assuming each social media brand is allocated to their own conversation referrer, then this proposed solution should hold true; as the convo-referrer would be the distinguishing factor.

But, if the same convo-referrer is to be used across different social media brands, then we would have to rethink our approach...

I'm not too sure if you've already set things up on the Echo side of things, but it might be worth dropping them a quick line to confirm a convo-referrer per social media brand would not be an issue...

[JCooper1979]

@kodinkat is convo-referrer the same as a permission set within Echo?

I have asked Echo about this and the response was vague. They said, "Unfortunately, we didn’t make the disciple tool integration it was created by MII. Echo could certainly send the source information out but it sounds like they aren’t pulling that in. The integration is not something we have built so we don’t have a way to assist much with this."

The way we have it set up in Echo is that one Permission Set contains multiple sources (FB, Instagram, Email, etc)... and the Digital Responder simply submits outcomes within this permission set which are forwarded to Disciple.Tools, which currently displays simply as Echo as the source in DT.

[kodinkat]

@JCooper1979 - Honestly speaking, I'm unsure whether convo-referrer directly translates to an Echo permission set, as terminology differ, I'd need to get eyes on...

Would it be possible to access or see screenshots of your current Echo system config setup; especially around Permission Sets; to get a better idea of things...?

[JCooper1979]

@kodinkat I could try to send you screenshots. I could also hop on zoom and try to show you.

[JCooper1979]

@kodinkat