Overview of Campaign and Reporting Endpoints

pentaleap provides an http based rest api to support integrations the endpoints described in this documentation are detailed with parameters and further information in the respective section for each this is an overview of what each endpoint is used for and some best practise for users of the endpoints access to the endpoints is dependent on each partner's use case, so not all endpoints are relevant for every partner organization, publisher, site and ad unit these endpoints describe how a retailer is set up and the available ad units (formerly called ad grids) they run on their properties pentaleap supports both single and multi publisher retailers as standard and will provide an organisation id to all new retailer partners these might be different banners within one market or across geographies brands and advertisers can be shared across organizations for easy campaign setup and management so advertisers can manage multi retailer campaigns seamlessly publishers are distinct retailers within an organization, typically a banner within a retail group the publisher endpoints allow users to retrieve information about each publisher including the products and brands available under each publisher and the id of each publisher, which is used for further operations each publisher also has one or more sites under them, for example a retailer may have different sites set up for desktop and app, or for different geographic markets site ids and names are retrieved from the sites endpoint each site is tied to a particular product feed (set up by the retailer and not relevant for the scope of this documentation), and each market (eg us, gb, mx) has its own product feed and currency ad units are the ad units a retailer has set up in their various publishers, markets and sites and which are optionally available for ad group targeting the ad unit endpoint retrieves a list of available ad units for a publisher and site while each ad unit is named, the locations and page positions are most relevant for any targeting purposes product the product endpoint retrieves sku level information for a specific publisher and site it can be used to see which products are present in the retailer product feed for sponsorship and inclusion in ad groups advertiser, campaign, ad group and spa ad group product these endpoints are used for advertiser, campaign, ad group creation and management via pentaleap's first party dsp, as well as reporting on ad group performance and status advertisers access is managed by the retailer and is designed to be flexible depending on the retailer setup an example structure is shown below retailers can grant access to all or a subset of available publishers, and retailers also assign available brands to each advertiser within and across publishers advertisers create ad groups within one publisher at a time, but can target any and all of their associated brands and products within an ad group ad groups can also target specific retailer locations such as search, homepage and category, but this is optional we recommend that ad groups default to targeting across all locations since pentaleap adserving technology is designed to place ads in the most relevant place in real time the advertiser endpoints allow users to retrieve (and if applicable create and update) advertiser information this includes the brands, locations and sites they are eligible to target multiple advertisers can be allocated against the same brand, but this will be listed specifically in the advertisers brandadvertiseroverlap field to avoid unwanted crossover of brands the campaign endpoints are used to create and report on campaigns for a specified advertiser this includes choosing markets and overall budgets for underlying ad groups the ad group endpoints allow users to manage ad groups including locations to target, dates, budget settings, setting them live or pausing them as well as adding default bids ad group products endpoints are used to set and update product level bids and settings to optimise ad groups there are also endpoints to help filter and bulk edit settings for groups of products belonging to specific brands or categories nb targeting locations are available within the ad group setup options, however we typically recommend to target all locations by default, as pentaleap relevancy technology specialises in only placing ads where they are naturally relevant to the customer's need publisher reporting and reporting status for users with publisher level access, these endpoints are used to create retailer level ad group reports at granular and aggregated levels for specified dates the reporting status endpoint returns the last update time for reporting so users know the last reported data point to support daily or regular calls to the reporting