Push daily capping

​@Silvio6 Validate all of this,

• UTC reset, not local time – daily caps reset at 23:59:59 UTC. The daily frequency cap is valid for the day until 23:59:59 UTC and resets to 0 at the start of the next day, and this expiry applies regardless of when the rule was created. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/conflict-prioritization/capping-rules/channel-capping
• Shared rule set across all push sends – if multiple journeys/campaigns each use their own rule set, counters don't share — a user can hit the cap in Journey A and still get push from Journey B. Confirm all push-sending journeys/campaigns reference the same rule set.
• Identity fragmentation (Race condition) – push identities (multiple devices/tokens) that haven't fully merged into one profile can each be evaluated separately, letting the same person get capped on one device but not another. Check the identity merge policy.
• Non-retroactive rule – a rule attached mid-day doesn't count sends that happened before it was applied, so early-day sends won't count toward the cap.
• See if you can reproduce the issue with the assurance.

@Silvio6, please verify the following:

• Confirm that daily frequency capping is enabled for your organization/sandbox. This feature is currently Limited Availability and is documented for campaigns and journeys using batch segmentation.
• If the cap must apply across multiple Push journeys or campaigns, configure one applicable channel rule set and ensure every relevant Push message or journey action uses it. For a custom rule set, confirm that both the rule and rule set are active.
• Select the highest-priority identity namespace when authoring the campaign or journey. Also verify that the recipient’s push tokens are associated with the intended profile; multiple tokens or devices can belong to one profile.
• Daily caps remain valid until 23:59:59 UTC and reset at the start of the next UTC day. The reset is not based on rule-creation time or the user’s local time.
• After activating or updating the rule, allow at least 10 minutes before sending. Counters update after delivery, so closely timed or high-volume sends may not be reflected immediately. Adobe recommends spacing communications where possible.
• Reproduce the issue with a new test profile and check the Live report or Customer Journey Analytics report for frequency-cap exclusions.

If the issue persists, collect the campaign/journey ID, Push action, rule-set configuration, identity namespace, activation time, and send timestamps before contacting Support.

Hope this helps! Feel free to follow up if you need more details.

---------------------------------------------

Kaustav Ghosh Dastidar | Adobe