Media Strategies API - Release v1.12


#1

We have released an update for the Media Strategies API. The release includes the following changes…

New version of top_urls strategy

We have introduced a new version of the top_urls strategy. The new strategy version works just as version 1, accepting the same parameters and performing the same analysis. However, whereas version 1 returns just the url for each result, version 2 returns the url, title and summary for each result.

To call the new version of the strategy you specify version 2 in your parameters:

{
    "type": "strategy",
    "name": "example",
    "subscription_id": "cd99abbc812f646c77bfd8ddf767a134f0b91e84",
    "parameters": {
        "strategy": "top_urls",
        "version": 2,
        "parameters": {
            "keywords": {
                "any": ["cloud", "azure", "aws", "google cloud", "vmware"]
            },
            "audience": {
                "countries": ["united states"]
            },
            "comparison_audience": "global"
        }
    }
}

The result includes the title and summary for each article:

{
    "redacted": false,
    "unique_authors": 92000,
    "interactions": 103000,   
    "urls": [
        {
            "url": "http://example.com/content-1",
            "title": "Example title of the page",
            "summary": "Summary of the page...",
            "unique_authors": 10000,
            "interactions": 12000,
            "engagement_ratio": 1.4
        },
        ...
    ]
}

Audience definition using occupations

You can now use occupations when you define audiences for analysis. The new field is supported for both top-level and group-level audience definitions.

For example…

{
    "type": "strategy",
    "name": "example",
    "subscription_id": "cd99abbc812f646c77bfd8ddf767a134f0b91e84",
    "parameters": {
        "strategy": "top_urls",
        "version": 2,
        "parameters": {
            "keywords": {
                "any": ["cloud", "azure", "aws", "google cloud", "vmware"]
            },
            "audience": {
                "occupations": ["software developer", "software tester"]
            },
            "comparison_audience": "global"
        }
    }
}

Note that the list of valid occupations is now provided by the Reference Data API.