Trust & Transparency
A publisher says, "I don't want to share networks and channels because you will share it with other pubs, and you can steal my resources."
Potential answers include
A. "I understand your concern, but our contracts strictly prohibit us from sharing confidential information. Our goal is to grow your business, not undermine it."
B. "That's not how we operate. We have a strong reputation, and our privacy policy ensures your data is secure."
C. "We are only interested in optimizing your campaigns. Sharing network insights helps us understand your unique inventory and recommend the best solutions for your app"
D. "Can you specify what kind of 'resources' you're worried about us stealing? We need more details to address this."
We don't want to add a Webview because Apple can block our app
A. "I understand your concern about Apple's guidelines. Our Webview integration follows all of Apple's strict guidelines and best practices to ensure compliance and prevent any app rejections. We have a proven track record."
B. "Apple only blocks apps for specific violations, not just for having a Webview. What makes you think this?"
C. "Many successful apps use Webviews without issue. It's a common and accepted practice when implemented correctly."
D. "We can explore alternative integration methods if the Webview is a deal-breaker, though it might limit functionality."
We want to keep our app not game focused.
A. "Absolutely. Our offerwall is highly customizable. We can curate offers to primarily feature non-gaming apps, surveys, subscription trials, and other relevant content that aligns with your app's core purpose and user interests."
B. "That's a challenge, as gaming offers often have the highest payouts. Are you sure you want to limit your revenue potential?"
C. "We can filter out gaming offers, but your fill rate and eCPM will likely be impacted negatively."
D. "What kind of non-game offers are you looking for? We have a diverse portfolio."
It is your responsibility to prevent fraud on your solution
A. "Absolutely. Fraud prevention is a top priority for us. We employ multi-layered fraud detection technologies and dedicated teams to actively monitor and prevent fraudulent activities on our platform, ensuring the integrity of your traffic and our offers."
B. "We do our best, but publishers also have a role in traffic quality."
C. "Yes, and we have advanced systems. What makes you ask?"
D. "Are you experiencing fraud with other partners? We are different."
We don't want iOS, as you don't have an SDK right now.
A. "I understand your concerns about integration time. However, our iOS Web view is highly optimized for quick implementation, and we offer dedicated technical support to guide you through every step, minimizing risk and time investment."
B. "iOS traffic generally offers higher ARPU. You'd be missing out on significant revenue by excluding it."
C. "What specifically are your concerns about the integration time? We can show you our SDK documentation and integration guide."
D. "We can start with Android only if you prefer, and revisit iOS later when you're more comfortable."
No, the eCPM is too low.
A. "I understand your concern about eCPM. To help us understand why you feel it's low and to identify optimization opportunities, could you share details about your current eCPM goals and user segmentation?"
B. "Our eCPM is competitive within the market. What are you comparing it to?"
C. "eCPM can fluctuate based on many factors. Are you sure you're looking at the right metrics?"
D. "We can try to increase the bids on certain offers, but this might reduce fill rate."
Sorry, we cannot share much info there (regarding sensitive internal data/strategy they previously hinted at)
A. "I completely understand and respect your confidentiality. Could we perhaps discuss this in broader terms, or focus on general trends you're observing, without diving into specific proprietary details? Any high-level insights help us tailor our solution better."
B. "Without more information, it's difficult for us to provide the best recommendations."
C. "What specifically are you unable to share? We only need aggregated data."
D. "Okay, so what can you share?"
We do not have enough resources for that.
A. "I understand resource constraints are common. Our solution is designed for minimal resource drain on your end. We offer extensive documentation, dedicated technical support, and in many cases, we can handle much of the setup and optimization ourselves to reduce your workload significantly."
B. "How much time can you allocate? We can adjust our plan."
C. "What tasks specifically are you concerned about? Maybe we can find a workaround."
D. "Many publishers find the ROI outweighs the resource investment.
No, we're getting better results with other offerwall players.
A. "That's valuable feedback. Could you share what specific metrics or features are driving those better results for you? We're always looking to optimize and might be able to offer a customized solution that surpasses current performance."
B. "What makes you say that? Our data shows we are top performers in the market."
C. "Are you sure you've compared apples to apples? Sometimes, initial results can be misleading without a proper A/B test."
D. "Okay, thank you for your honesty. We'll check back in a few months.
Can you share the CPI for this advertiser?
A. "We cannot disclose specific advertiser CPIs as this is proprietary data. However, we can provide you with eCPM benchmarks relevant to your app's genre and audience."
B. "Why do you need the CPI? Our focus is on your overall revenue performance (eCPM)."
C. "We typically don't share CPIs, but if you sign an NDA, we might be able to provide some general ranges."
D. "The CPI varies greatly depending on geos and user quality. What kind of performance are you seeing on your end?"
We don't want to make any changes in the app.
A. "I understand the desire for minimal disruption. However, even small changes, like updating SDKs, are often necessary to access the latest features, security updates, and revenue optimizations. We aim for very low-impact integrations."
B. "Without any changes, it's impossible to integrate our solution. Our SDK requires some level of integration."
C. "Are you sure? Our competitors' solutions often require more significant changes than ours."
D. "What kind of changes are you specifically worried about? We can usually find a workaround."
We're planning to add a new offerwall.
A."That's great to hear about your growth! To ensure maximum efficiency and prevent cannibalization, let's discuss how our solution can seamlessly integrate alongside new partners, optimizing for unique demand and avoiding overlap. We often complement other solutions very well."
B. "Are they an offerwall partner? Because that might conflict with our solution."
C. "Why are you adding another partner? Are you not happy with our performance?"
D. "Okay, let us know when they're live."
"Can you share the postbacks by geos for a month for Coin Master?"
A. "We can provide aggregated performance reports, including a breakdown by geo for your specific campaigns with Coin Master, but we cannot share raw postback data from other publishers due to data privacy and confidentiality agreements."
B. "No, we don't share raw postbacks as it's proprietary data."
C. "What do you need that data for? We can give you an overall performance report."
D. "Sharing that level of detail is against our policy. We can show you trends, though."
We don't want to make any changes in the app this quarter.
A. "I understand you have a packed roadmap. Let's schedule a follow-up discussion for next quarter to ensure we're aligned with your development cycles and ready to integrate then."
B. "Could we explore integrating a smaller, less resource-intensive part of our solution, or perhaps just begin with a server-side integration that requires no app changes?"
C. "Are you sure there's absolutely no room? Our solution could significantly boost your revenue by the end of this quarter."
D. "That's a shame. You'll be missing out on a lot of potential revenue during this time."
Margin will be impacted as we are giving out extra rewards to users
A. "I understand your concern about margin. Our solution is designed to deliver a positive ROI. We can work with you to optimize your reward strategy, ensuring that any extra rewards you give out translate into significantly higher user engagement and offer completion rates, ultimately boosting your net revenue."
B. "Extra rewards are necessary to compete and drive higher user LTV."
C. "What kind of 'extra rewards' are you talking about? Our model accounts for standard rewards."
D. "That's a decision you'll have to make. We can't control your reward spending."