Chat #71

Claude Haiku 3.5

4 messages
4 chunks
20422 in
1115 out
$0.0208
Me
What’s the difference between Static and Formula CPM floor types?
Enki
I'll explain the differences between Static and Formula CPM floor types based on the documentation: **Static CPM Floor** **Source:** [CPM Percentile Configuration](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4244537368) ![Static CPM Configuration](https://tripledotstudios.atlassian.net/wiki/download/thumbnails/4244537368/image-20250526-144933.png) Key Characteristics: - Sends a fixed CPM value to the client - Always uses the same predefined value for bidding - Simple, predictable pricing strategy - Manually set by the user **Fields**: - **Fallback CPM Value**: A static floor value sent to MAX for bidding - Optional **Percentile Configuration** can be applied - Can define fallback behavior if no percentile data is available **Formula CPM Floor** **Source:** [Setting up Ad Units](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/4304109569) Key Characteristics: - Dynamically calculates CPM floor using historical data - Two calculation methods: 1. **Median**: Uses median of most recent N CPM values 2. **Average**: Uses average of most recent N CPM values Formula: - Median: _interstitial_cpm_floor = Median (most recent **N** CPM values) × **K**_ - Average: _interstitial_cpm_floor = Average (most recent **N** CPM values) × **K**_ **Advanced Configuration Options**: - Select calculation type (Median/Average) - Define N (number of recent CPM values) - Set percentage coefficient (K) - Choose behavior for insufficient data - Option to use only successful ad requests - Fallback mechanisms for failed/insufficient requests **Key Differences**: | Feature | Static | Formula | |---------|--------|---------| | Value Determination | Fixed, manual value | Dynamic, calculated from historical data | | Flexibility | Low | High | | Complexity | Simple | More complex | | Pricing Approach | Consistent | Adaptive | | Data Dependency | None | Requires sufficient historical CPM data | **Recommendation**: - Use **Static** for predictable, controlled pricing - Use **Formula** for dynamic, data-driven pricing that adapts to market conditions
Me
What’s the difference between Static and Formula CPM floor types? for Impressions Restrictions
Enki
Great question! Let me break down the CPM floor types for Impressions Restrictions based on the Analytics Buckets documentation. **Static CPM Floor for Impressions Restrictions** **Characteristics**: - Fixed, manually set CPM value - No dynamic calculation - Consistent pricing across all events - Simple to configure **Example Configuration**: - User directly inputs a specific CPM value - Same value used for all ad mediation platforms - No dependency on historical performance data **Formula CPM Floor for Impressions Restrictions** **Characteristics**: - Dynamically calculated using historical CPM data - Uses events from multiple buckets: - MAX Interstitial Buckets (0, 1, 2) - Google Interstitial Event Bucket - Meta Interstitial Event Bucket **Calculation Process**: 1. **Source Buckets**: All events from different ad networks 2. **Event Processing**: - Merge events from all buckets - Sort chronologically by timestamp - Select most recent events **Detailed Calculation Example**: - **Min Ad Requests to Apply Formula**: 3 - **Ad Requests to Use in Formula**: 4 - **Selected CPMs**: 5, 5, 6, 6 - **Calculation**: - Formula: (5 + 5 + 6 + 6) × 1.1 = 5.5 × 1.1 = 6.06 - **Final CPM Floor**: 6.06 **Key Differences**: | Feature | Static CPM | Formula CPM | |---------|------------|-------------| | Value Origin | Manual input | Calculated from historical data | | Complexity | Simple | More complex | | Adaptability | Fixed | Dynamic | | Data Dependency | None | Requires sufficient recent events | | Calculation Method | Constant value | Median/Average with multiplier | **Important Notes**: - Currently only available for Interstitials - Requires sufficient historical event data - Pulls data from MAX, Google, and Meta buckets - Allows fine-tuning with min/max request settings - Provides flexibility in pricing strategy **Recommendation**: - Use **Static** for predictable, controlled pricing - Use **Formula** for adaptive pricing that reflects recent performance trends