Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Prerequisites

Step Summary

  1. Add the Initialization code.

  2. Follow our ad format guides for their implementation.

  3. Test everything is working

  4. Change everything to production code

  5. Your app is now prepared for monetization with us.

We only mention how to create wrappers and not triggers because the way a trigger is fetch for its use is highly dependant on your specific app code.

Wrappers and Triggers/Events are used for different formats, each ad format page tells you what you need to use (wrapper or trigger) to display it.

Initialize the SDK

Use the R89SDK.initialize(...) method to initialize the SDK.

R89SDK.setLogLevel(LogLevel.debug); //This is for testing purposes, remove it on prod
R89SDK.setDebug(); //This is for testing purposes, remove it on prod
R89SDK.initialize(
      publisherId: "TestRefinery89ID", /* This is for testing purposes, change it on prod */
      appId: "TestDemoApp", /* This is for testing purposes, change it on prod */
      singleTag: true);

Your publisherId and appId will be provided to you during onboarding process by email, you can also retrieve them from the web interface after login.

This appID is not the same as the Manifest App Id or the Info.plist GADApplicationIdentifier you used in previous steps.

Add navigation observer.

Just before starting to put R89Tag widgets into your widget tree, make sure to add R89SDK.routeObserver to your navigatorObservers list

@override
Widget build(BuildContext context) {
  return MaterialApp(
    navigatorObservers: [
      R89SDK.routeObserver,
    ],
    // ...
  );
}

Follow our Ad Formats guides

Go into production

For going into production you will need to use your ids:

  • Remove the methods R89SDK.setDebug() and addTestingSingleTagData() .

  • Change the App ID in the manifest for the production one.

  • Change the GADApplicationIdentifier in the info.plist for the production one.

  • Change the appId and publisherId in the initialization method for the production ones.

  • it’s also recommended to remove R89SDK.setLogLevel(LogLevels.DEBUG) but not needed.

How does it work?

We fetch all ad unit configurations from our Database and you simply need to place the ad units using the R89 Ad widgets and the r89ConfigurationIDs we provide you. Incorporate them into the desired views.

Check Flutter - Ad Formats to see how each format is implemented.

  • No labels