Skip to Content
Oct 31, 2017 at 12:29 PM

Hybris Marketing Twitter ID



I have noticed from standard Odata examples that SAP expects that it will be plausible to hold a Twitter ID against the contact. What is the actual use case for this? Social listening uses queries against key words rather than Account IDs.

The only thing I can think of for this is to link Tweets to a known contact so that you can analyse tweets from known individuals rather than a stack of unknown. So the next question is around the contact creation process on tweets. I understand from existing demos that tweets absorbed through social listening will create a contact if the report CUAN_IC_MASTERDATA_EXTR_DELT is run. Is there anyway of preventing new unknown contacts from being created when the twitter Id doesn't match an existing contact but still have access to the data in Social Sentiment app? I'm conscious that it will take up the limit on contacts that we hold licenses for.