PMax Listing Group Status and Asset Group ID Discrepancy

[rdhmdhl]

PMax Listing Group Status and Asset Group ID Discrepancy

[rdhmdhl]

I've observed that when I include the asset_group.status field in the AND clause of the query, it accurately selects the intended asset group, as evidenced by the correct asset group ID being returned in the response. Subsequently, this adjustment also results in the accurate representation of the listing group status.

Prior to incorporating the asset_group.status into the AND clause, the query was erroneously retrieving an asset group marked as "Removed". Despite this, the listing group associated with this incorrect asset group displayed metrics identical to those visible in the browser interface.

Could anyone shed light on why the query behaves differently without specifying the asset_group.status in the AND clause? Is this expected behavior, or might it indicate a potential issue with how the query filters based on the status field? Removed asset groups are not viewable within the browser UI.

Here's the new query:

    SELECT    
        asset_group.name,
        asset_group.resource_name,
        asset_group_listing_group_filter.resource_name,
        asset_group_listing_group_filter.type,
        campaign.id,
        asset_group.status
    FROM asset_group_product_group_view
    WHERE campaign.id = {campaign_id}
    AND asset_group.status = 'ENABLED'
    AND asset_group_listing_group_filter.case_value.product_item_id.value = '{product_id}'
    AND asset_group.resource_name NOT IN ('{resource_name}')
    LIMIT 1

[BenRKarl]

Hi @rdhmdhl - this looks like an issue with the API itself and not this library. I recommend reaching out to our API support channel here