AI assistants like ChatGPT, Gemini, and Grok can be powerful analysis partners — when properly structured. Because Godcaster exports include structural nuances (attribution fields, action types, device indicators, session reconstruction limits, timestamp precision, and play-counting rules), how you prompt the AI directly affects accuracy. To produce consistent, board-ready reports, Godcaster recommends using our developer tested and authenticated prompts. Computation is separated from narrative to improve reliability across AI tools.

How to Use This
• Export your monthly performance CSV from the Godcaster dashboard
• Open your AI assistant (ChatGPT, Gemini, etc.)
• Upload the CSV
• Copy prompts and run it
• Do not shorten the prompts, as the structure is what ensures accuracy

Purpose

Analyze only the uploaded Godcaster Digital Station export(s).

Every metric, observation, recommendation, and conclusion must be supported directly by the uploaded export(sA).

Do not use:

• Aptabase
• Internal analytics systems
• Previous reports
• Previous conversations
• Websites
• Outside knowledge
• Historical information not contained within the uploaded export(s)

If the data does not support a conclusion, clearly state the limitation rather than speculating.

Writing Standards

Write this report as though presenting it personally to the station's General Manager and Board of Directors.

The report should be:

• Executive
• Professional
• Warm
• Encouraging
• Objective
• Evidence-based

Help leadership understand:

• What happened
• Why it matters
• What should continue
• What practical next steps should be considered

Do not simply repeat statistics.

Interpret them.

Explain why the numbers matter, not merely what they are.

Favor insight over completeness. When forced to choose between presenting another statistic or explaining why an existing statistic matters, prioritize interpretation.

When multiple metrics support the same conclusion, synthesize them into a single executive observation rather than discussing each metric independently.

Celebrate accomplishments supported by the data while honestly acknowledging opportunities for growth.

Avoid technical jargon whenever possible.

Avoid promotional language.

Avoid unsupported conclusions.

Recommendations should prioritize helping the station make fuller use of capabilities already available within its existing Godcaster Digital Station.

Do not recommend purchasing additional Godcaster products or services.

Reporting Definitions

Use these definitions consistently throughout the report.

Support classifications:

• support:program = Program Support
• support:player = Station Support
• support:player_rss = Station Support

Rules:

• Support Actions are not donations unless explicitly confirmed.
• Progressive Web App (PWA) activity is not an installation unless installation events exist.
• Technical identifiers are not verified listeners.
• Plays are already de-duplicated to one Play Event per listener per hour. Do not perform additional de-duplication.

Data Validation

Before writing the report, verify:

• Reporting period
• File structure and column headers
• Distinct Action values
• Program and Episode availability
• Device, Platform, App and Referer fields
• Timestamp precision
• Presence or absence of Session IDs
• Missing or unexpected values affecting interpretation
• Any limitations affecting confidence

Determine whether reliable session reconstruction is possible using IP + User Agent with a 30-minute inactivity timeout.

If timestamps lack sufficient precision, explain why reliable session reconstruction cannot be performed.

Executive Report

Executive Summary

Begin with an Executive Summary of approximately 250–400 words.

Answer these questions in order:

• What happened?
• Why does it matter?
• What is the station doing particularly well?
• What is the greatest opportunity for improvement?
• What should leadership pay attention to next month?

Write this section as a narrative.

Do not simply repeat KPI values or table contents except where necessary to support the narrative.

Leadership Takeaways

Provide five concise executive takeaways.

Each should be a complete leadership insight rather than simply restating a statistic.

KPI Summary

Provide a summary table including, where available:

• Total Engagement
• Total Listening
• Play Events
• Resume Events
• Estimated Listening Reach
• Estimated Overall Engagement Reach
• Live Listening
• On-Demand Listening
• Shares
• Support Actions
• Follow Activity
• Progressive Web App (PWA) Activity

After the table, summarize the overall significance in one concise paragraph.

Do not explain every KPI individually.

Audience Reach

Clearly distinguish between:

• Estimated Listening Reach
• Estimated Overall Engagement Reach

Do not present technical identifiers as verified listeners.

If listener estimates are based on IP addresses or IP + User Agent combinations, briefly explain the methodology and resulting limitations.

Digital Platform Performance

Always report separately whenever the export permits:

• Website
• Progressive Web App (PWA)
• Godcaster Mobile App
• Generic Godcaster Player

Never merge these categories into a single "Web" or "App" figure.

If attribution is incomplete, explain why.

Interpret what the platform distribution indicates.

Listening Performance

Include:

• Play Events
• Resume Events
• Total Listening
• Average Daily Listening

Also summarize, where available:

• Listening by Platform
• Listening by Device
• Website Listening
• Progressive Web App Listening
• Godcaster Mobile App Listening

Interpret what the listening patterns indicate without speculation.

Content Performance

Include:

• Top Programs
• Top Episodes (when available)
• Live Listening
• On-Demand Listening

Discuss what the distribution of listening suggests about programming diversity, concentration, and audience breadth.

Do not speculate about listener motivations.

Listener Engagement

Break Engagement into:

• Listening
• Navigation
• Response
• Ownership
• System

Explain what each category represents.

Identify where RSS activity has been classified.

Avoid simply restating table values.

Explain what the engagement mix reveals about how listeners are using the Digital Station.

Support Activity

Report:

• Program Support
• Station Support
• Total Support Actions

Explain where support activity is concentrated.

Do not describe Support Actions as donations or completed gifts.

Insert Performance

If insert data exists, report:

• Insert Views
• Insert Clicks
• Best Performing Content

If insert activity is unavailable, simply state that insert performance could not be evaluated from the uploaded export.

Device & Platform Usage

Provide tables summarizing:

• Devices
• Platforms

Include Engagement and Listening where available.

Following each table, provide no more than one concise interpretation paragraph highlighting only the most meaningful findings.

Listener Behavior

Discuss only behaviors directly supported by reconstructed sessions or timestamp sequences.

If reliable session reconstruction is not possible, simply state:

Reliable listener journey analysis could not be performed because the export does not contain sufficient session information.

Do not speculate beyond the available evidence.

Strategic Opportunities

Provide three to five practical recommendations.

Each recommendation must include:

• Evidence from this report
• Why it matters
• Practical next step
• Expected benefit

Reference specific findings from this report whenever possible rather than generic digital best practices.

Recommendations should strengthen use of capabilities already available within the customer's existing Godcaster Digital Station.

Data Confidence & Limitations

Summarize only those limitations that materially affect interpretation of this month's report.

Do not repeat definitions or limitations already explained elsewhere.

Executive Conclusion

Conclude by summarizing:

• Greatest accomplishment
• Strongest encouraging trend
• Most significant opportunity

Do not introduce new findings in the conclusion.

Finish with a positive, forward-looking statement fully supported by the data.

Final Validation

Before finalizing, verify that:

• Every number matches the uploaded export.
• Every percentage uses the correct denominator.
• Listening Reach and Overall Engagement Reach are clearly distinguished.
• Website, Progressive Web App, Godcaster Mobile App, and Generic Godcaster Player are reported separately whenever possible.
• Live and On-Demand listening are reported whenever supported by the export.
• RSS activity has been consistently classified.
• Recommendations are supported by evidence from the report.
• Every recommendation includes a practical next step.
• The report explains why the numbers matter, not simply what they are.
• The report favors executive insight over exhaustive statistics.
• The report reads as one coherent executive narrative.
• No unsupported conclusions or outside knowledge have been introduced.

End copy.