interaction.tag_tree

Analyze this target to count the number of interactions on which a particular VEDO tag has been applied.

This target is not available for Interaction Filtering. It is available for use in Analysis Queries and Query Filters.

In the current release namespaces must be lowercase only.

See also: interaction.tags.

Examples

The way you use this tag depends on the CSDL you run in your Interaction Filter. For example, this Interaction Filter:

tag.device "Hauwei" { interaction.source contains "Hauwei" } 
tag.device "HTC" { interaction.source contains "HTC" } 
tag.device "iPhone" { interaction.source contains "iPhone" } 
tag.device "LG" { interaction.source contains "LG" } 
tag.device "Nokia" { interaction.source contains "Nokia" } 
tag.device "Samsung" { interaction.source contains "Samsung" } 
tag.device "Sony" { interaction.source contains "Sony" } 

return {     
    interaction.content contains "Venice" OR links.title contains "Venice" 
}

will create tags in the interaction.tag_tree.device namespace. Your analysis query might be:

{
    'analysis_type': 'freqDist', 
    'parameters': {
        'threshold': 6, 
        'target': 'interaction.tag_tree.device' 
    } 
}

Notes

Note that when using interaction.tag_tree as a query filter target, append the full path of your tag tree to the end of the target itself, just like you do when using interaction.tag_tree as an analysis target. For example, this rule constrains your analysis to interactions to which a particular tag were applied:

interaction.tag_tree.animals.sea_creatures == "lobsters"

To restrict results to all the tags in this branch you must specify full tag tree path by customizing the target:

interaction.tag_tree.animals.sea_creatures exists

For scored tags, your predicate must be a tag tree as tag leaves are not allowed in scored tags:

interaction.ml.categories == "animals.sea_creatures"

Resource information

Target service: PYLON for Facebook Topic Data

Target object: Interaction

Type: array(string)

Array: Yes

Tokenized for query filters: No

Interaction filter: No

Analysis target: Yes

Query filter: Yes

Child analysis target: No