Browse the help center

Match stale location targeting to current places with AI

The suggestions of GET on this path, with the places names leave open sent to the AI assistant's model, which picks only from the geo database's own list: in as few calls as the lists allow, at most 12 of up to 60 places, four at a time, and the request waits for them at most two minutes.

Reference
POST https://YOUR-NETWORK-DOMAIN/rest-api/targeting/stale-locations/suggestions.do

The suggestions of GET on this path, with the places names leave open sent to the AI assistant's model, which picks only from the geo database's own list: in as few calls as the lists allow, at most 12 of up to 60 places, four at a time, and the request waits for them at most two minutes. It runs and is billed like the AI assistant - it needs the AI_ASSISTANT_CHAT permission, a key and monthly budget left, and the budget is checked again before each call after the first four. A place another request is asking about at the same moment is not asked twice. Rules naming the same stale place with the same include or exclude form one group, with its 'targetIds', how many rules of each kind and how many entities of each level carry them. 'suggestion.action' is REPLACE (apply with POST replace.do: targetIds, countryCode, regionName, cityName as the suggestion gives them), REMOVE (no current place matches, and removing the rules changes nothing: POST remove.do) or KEEP (nothing is proposed: removing the rules would change delivery, or the geo service did not answer for the place; the user decides). A city whose region is gone is looked for under up to 80 of the country's regions; where the country has more, not finding it there is a NO_SUCCESSOR of LOW confidence. 'reason' is SPELLING, SUFFIX (an administrative word such as "County" or "Stationsby" dropped), REGION_RENAMED, RENAMED, MERGED, NO_SUCCESSOR, NOT_MATCHED, COUNTRY_RULE or GEO_UNANSWERED, with 'reasonParams' (old name, new name) and 'reasonText' in the user's language; 'confidence' is HIGH, MEDIUM or LOW; 'source' says whether names (DETERMINISTIC) or the AI assistant's model (AI) matched it. 'ai' says what happened: USED, NOT_NEEDED (every place was answered already), DISABLED, PERMISSION, NO_KEY, LIMIT or FAILED; without the model the suggestions come from names alone and 'aiMessage' says why. Answers are kept in the server's memory for up to a week, until it restarts, for every user. Nothing is changed. Requires MANAGE_DEMAND_TARGETING or MANAGE_SUPPLY_PRE_TARGETING.

Responses

200

{success, status: OK|GEO_UNAVAILABLE, unavailable, message, ai, aiMessage, groups:[{type, value, place, rule, targetIds, kinds:{SAFE, OPENS_ALL, STARTS_DELIVERY}, entities:{ADVERTISER, CAMPAIGN, BANNER, SITE, ZONE, PLACEMENT}, suggestion:{action, countryCode, regionName, cityName, newPlace, reason, reasonParams, reasonText, confidence, source}}]}

400

Bad request — invalid or missing parameters

401

Authentication error

403

The role lacks both MANAGE_DEMAND_TARGETING and MANAGE_SUPPLY_PRE_TARGETING

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.