Example LinkedIn Interactions

Now that you have an overview of the data model and targets that are available, we'll next look at some example interactions to see how the targets are populated.

We'll use 'Emma' as an example member who starts by writing a post. Her contacts engage on her post and we'll look at how the target namespaces are populated for each interaction.

Example activities

A member posts a share

Emma is writing and sharing an update about her plans:

share

This is the share as seen on her contacts' timeline:

share-posted

When Emma posts this share it creates an interaction. PYLON receives the interaction and populates targets with attributes of the share. The following targets and namespaces are populated:

Namespace / target Value / description
li.type activity
li.subtype activity|share
li.media_type post (because there is no link in the share)
li.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector.
li.all.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector.
li.user.member.* Populated with Emma's demographic details.
li.user.member.type member
li.user.company.* Not populated because Emma is a member.
li.root.* Not populated because this is a share activity.
li.all.mentions.* Companies mentioned in the share.
li.all.mentions.company_names Citigroup

A member engages with the share

Charlie is one of Emma's contacts, he chooses to like her post. The like is seen on other member's timelines like this:

like

The like creates a new interaction that is received by PYLON. Attributes of the like, and the post being liked are used to populate targets and namespaces as follows:

Namespace / target Value / description
li.type share
li.subtype activity|like
li.media_type post (this is the type of the share engaged with)
li.content Not populated because this is a like.
li.all.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector. (populated from the share being enaged with)
li.user.member.* Populated with Charlie's demographic details.
li.user.member.type member
li.user.company.* Not populated because Charlie is a member.
li.root.* Populated with details of the share being enaged with.
li.root.member.* Populated with Emma's demographic details.
li.all.mentions.* Companies mentioned in the share enaged with.
li.all.mentions.company_names Citigroup

A member comments on the share

Hugo comments on Emma's post, this creates a new interaction. The main difference between Charlie's like and Hugo's comment is that a comment has content.

comment

Targets are populated with the content of the comment and the root share activity.

Namespace / target Value / description
li.type share
li.subtype activity|comment
li.media_type post (this is the type of the share engaged with)
li.content I'll be in the audience - interested to hear what Signature Bank make of your presentation.
li.root.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector.
li.all.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector.
I'll be in the audience - interested to hear what Signature Bank make of your presentation.
li.user.member.* Populated with Hugo's demographic details.
li.user.member.type member
li.user.company.* Not populated because Hugo is a member.
li.root.* Populated with details of the share being enaged with.
li.root.member.* Populated with Emma's demographic details.
li.all.mentions.* Companies mentioned in the share enaged with or the comment.
li.all.mentions.company_names Citigroup, Signature Bank

A member likes the comment

Next Charlie likes Hugo's comment.

like-comment

Now we have a chain of activities. The targets are populated with details of Charlie's like and Emma's root share, but not with the intermediate comment from Hugo.

Namespace / target Value / description
li.type share
li.subtype activity|like
li.media_type post (this is the type of root share)
li.content Not populated because this is a like.
li.all.content I'll be presenting at the Citigroup conference next week, talking about cloud computing and virtualization in the public sector. (populated from the share being enaged with)
li.user.member.* Populated with Charlie's demographic details.
li.user.member.type member
li.user.company.* Not populated because Charlie is a member.
li.root.* Populated with details of the share being enaged with.
li.root.member.* Populated with Emma's demographic details.
li.all.mentions.* Companies mentioned in the share enaged with.
li.all.mentions.company_names Citigroup

A member shares an external article

The previous examples used the share of a post. In the next examples we'll look at the extra information available when the share is of an article.

Emma is going to share an external article. She does this by including a link in her post.

external-article

LinkedIn follows the link and collects metadata about the page from the <meta> tags on the page. In this example, LinkedIn have used the title, description, image and URL tags in the share.

<meta property="og:title" content="Apple's iPhone 7 ditches traditional headphone socket - BBC News" />
<meta property="og:type" content="article" />
<meta property="og:description" content="Apple confirms that its new iPhone will not feature a traditional headphone socket." />
<meta property="og:site_name" content="BBC News" />
<meta property="og:locale" content="en_GB" />
<meta property="article:author" content="BBC News" />
<meta property="article:section" content="Technology" />
<meta property="og:url" content="http://www.bbc.co.uk/news/technology-37277965" />
<meta property="og:image" content="http://ichef-1.bbci.co.uk/news/1024/cpsprodpb/57A4/production/_91063422_mediaitem91063421.jpg" />

The usual user member targets are populated (with Emma's details), and now the article areas of the namespace can be populated with details of the external article. However, with external articles the article author is not knowable so this namespace remains unpopulated.

Namespace / target Value / description
li.type activity
li.subtype activity|share
li.media_type article (because there is a link in the share)
li.content Can't believe Apple have dropped the headphone socket...
li.all.content Can't believe Apple have dropped the headphone socket...
li.user.member.* Populated with Emma's demographic details.
li.user.member.type member
li.all.articles.* Populated with details of the article.
li.all.articles.type external
li.all.articles.domain bbc.co.uk
li.all.articles.url http://www.bbc.co.uk/news/technology-37277965
li.all.articles.title Apple's iPhone 7 ditches traditional headphone socket - BBC News.
li.all.articles.summary Apple confirms that its new iPhone will not feature a traditional headphone socket.
li.all.article.author.* Not populated because the article is external to LinkedIn.
li.all.mentions.* Companies mentioned in the share or article.
li.all.mentions.company_names Apple

A member shares a LinkedIn article

If Emma had chosen to share an article on LinkedIn then the li.all.articles.author.* targets would be have been populated with demographic details of the author of the article.

Example events

Carrying on from the example above we'll now look at events in the same way.

A member clicks on a shared article

Charlie clicks on Emma's External Article share, generating a click event.

click

The click has created a new interaction that is received by PYLON. Attributes of the click, and the article being clicked are used to populate targets as follows:

Namespace / target Value / description
li.type click
li.subtype click|view
li.media_type article (because there is a link in the share)
li.content Not populated as a click has no content.
li.user.member.* Populated with Charlie's demographic details.
li.user.member.type member
li.all.articles.* Populated with details of the article in the share.
li.all.articles.title Apple's iPhone 7 ditches traditional headphone socket - BBC News.
li.all.article.author.* Not populated because the article is external to LinkedIn.
li.all.mentions.* Companies mentioned in the share or article.
li.all.mentions.company_names Apple
li.root.* Populated with details of the share being clicked on.
li.root.user.member.* Populated with Emma's demographic details.
li.root.content Can't believe Apple have dropped the headphone socket... (the content of the share being clicked)
li.all.content Can't believe Apple have dropped the headphone socket... (the content of the share being clicked)

A member views an external article

Now Charlie has clicked the share, he is viewing the content. This generates an article view event.

Note that not all content on all domains will trigger an article view event.

Targets for the event are populated as follows:

Namespace / target Value / description
li.type article_view
li.subtype article_view|article_view
li.content Not populated as a view event has no content.
li.user.member.* Populated with Charlie's demographic details.
li.user.member.type member
li.all.articles.* Populated with details of the article being viewed.
li.all.articles.title Apple's iPhone 7 ditches traditional headphone socket - BBC News.
li.all.article.author.* Not populated because the article is external to LinkedIn.
li.all.mentions.* Companies mentioned in the share or article.
li.all.mentions.company_names Apple
li.root.* Populated with details of Emma's share.
li.root.user.member.* Populated with Emma's demographic details.
li.root.content Can't believe Apple have dropped the headphone socket... (the content of the share being clicked)
li.all.content Can't believe Apple have dropped the headphone socket... (the content of the share being clicked)

A member views a LinkedIn article

Again, if Emma had chosen to share an article on LinkedIn then the li.all.articles.author.* targets would be have been populated with demographic details of the author of the article.

A member expands a share or comment

As well as the events described above, there is also the 'expand' click type. This event occurs when a member clicks a 'show more' link on a newsfeed activity or comment.

For this event the value of li.subtype is 'click|expand'. The same targets are populated as for the click event as described above.

Article view without a preceding click event

An article view event can be received without a corresponding click event when someone clicks on a link to a LinkedIn article from outside of LinkedIn.

In this case li.subtype will equal article|view.

Because the article has been posted on LinkedIn the targets in the li.all.articles.author.* namespaces will be populated, as the author is known.

Next steps...

Now that you have an in-depth undestanding of the target and namespaces, next you'll learn how to configure identities which you'll use to run your analysis queries.

Managing identities