FAQs
From QuattroWiki
Contents |
Revenue and Payment FAQs
Q. Net Revenue Transition. What does this mean to publishers?
A. We've received feedback from publishers to display their share of earnings within our reporting portal. This will help our clients easily understand how much revenue they're earning within our network. As of October 1st, Quattro's reporting portal has been updated to reflect Net Revenue instead of Gross Revenue for current and recent data since June 1, 2009. Any data prior to June 1, 2009 is still be accessible and will be reported as Gross Revenue.
Q. When does Quattro Wireless remit payment to publishers?
A. Once you reach $100 USD, Quattro pays publishers NET 60 following the end of that calendar month. Allow 2 weeks of payment processing and mail time. For example, if you reach $100 on March 10, you will receive your payment around the second week of June.
Quattro Mobile Site FAQs
Q. I'm getting the following error. What should I do?
<!-- message code [4002] : description [Invalid data.] : details [Invalid [pid] parameter value [183469aa521f94cc7b9f952d1d9bef211]] message code [4000] : description [Bad request.] : details [Bad request. Parameter [sid] missing.] --> <!-- no qualified ads found for this request -->
A. Validate that your request includes your unique Publisher Account ID and the correct Site ID. The correct IDs are included in the ad tags that are generated for you when you create or manage your site settings. Check your request against the ad tags to ensure you’re sending the right IDs.
Q. I'm getting this error. Now what?
<?xml version="1.0" encoding="UTF-8"?>
<qwads version="2.0">
<ads />
<status code="success">
<messages>
<message code="2001" description="no qualified ads found for this request">No ad response
generated from strategy tag [54177335e3954b76a88942821cebd180].
</message>
</messages>
</status>
</qwads>
A. There are a number of reasons why you may not get qualified ads. A common problem is that a request not be sending the correct device, carrier or country data. Verify that the correct user agent is specified in the request, as the user agent defines the device. You should also check that you are sending the IP address from the device (not the IP from your server), as Quattro uses this information to direct carrier and country targeting. Finally, ensure that you are also forwarding HTTP headers sent from the device in the ad request. This will further improve carrier detection and indicate support for cookies that certain classes of ads may require.
If technical integration issues have been ruled out as problems, then other factors that may affect ad availability include restrictions defined on the part of the publisher (e.g. advertiser blacklists, content classification, etc.), or general lack of ads (which can be sensitive to the time of day, serving restrictions, etc.).
Q. What kind of extra targeting parameters does Quattro support?
A. Quattro's API accepts a wide range of geographic and demographic parameters. Specifying values for these parameters can help you increase your ad fill and CPM rates. You can specify geographic targets such as area code and zip code, and demographic targets such as gender, age, and income. To see the full list of values for these parameters, see Enhance Your Targeting.
Q. How do I identify different sections of my site, and define different ad preferences and restrictions for those sections?
A. Quattro enables you to identify different parts of your site that have similar characteristics. You can tag similar content areas by using the cid parameter. For example, if you have several pages that relate to cars, you can tag them with cid=cars. Advertisers can then target ads that go well with that content. If you use the cid parameter, you must give Quattro the string you use in order to setup matching information on the Quattro Mobile Ad Platform. Contact your Quattro Account Manager for assistance.
Q. How do I specify criteria for certain types of ads to appear in specific places on my page?
A. You can specify either top, middle or bottom placement on a page by using the plc parameter. It's recommended to specify placement, as many advertisers require it in order to serve their ads. You can use any of the following values:
- t=top
- m=middle
- b=bottom
Q. How can I specify which type of ad I want - banner, text, interstitial or expandable?
A. Use the adm parameter to choose the type of ad you want. You can use any of the following values:
- a=any static banner, animated banner, or text ad
- b=static or animated banner
- t=text ad only
- i=interstital ad
- sa=expandable ad
To specify more than one type, use comma delimited values. You can use URL-encoded, comma delimited values to specify multiple types. For example, if you want banner, text and interstitial ads: b,t,i then use URL-encoded: b%2Ct%2Ci. Note that when you use this in conjunction with the plc parameter, you can specify the kind of ad that appears in the place you want.
Q. I've defined my adm parameter - why am I still not seeing those ads?
A. If you've defined your adm parameter and you're still not seeing the ads you've specified, please contact support@quattrowireless.com to resolve the issue.
Q. I’ve tested the integration and I’m ready to go live. What should I do?
A. Let us know you’re ready to go live by submitting your site for approval. To do that, go into “Manage Sites”, select your site, and click the Submit for Approval tab. Once ads start to be served on your site, Quattro begins to optimize your eCPM. The algorithms will gradually include more relevant and premium ads over the first 48 hours once you’ve launched. Please be patient as we work to optimize your performance. If you have any questions, please contact your Quattro Account Manager.
Quattro iPhone SDK FAQs
Q. When should I use the SDK for OS 2.0, and when should I use the SDK for OS 3.0?
A. It depends on which platform your application is built:
- If your application is built on iPhone OS 2.x, use the SDK for 2.0. This version is compatible with applications built for both iPhone OS 2.x and iPhone OS 3.x.
- If your application is built on iPhone OS 3.x and uses its latest features, use the SDK for 3.0.
Q. I'm getting this linker error. What do I do?
2009-03-01 22:32:45.446 App Name[552:6507] *** -unrecognized selector sent to instance 0x1088940
A. On the Build tab, include the ObjC flag in the Other Linker Flags setting, and:
- Apply the setting across all configurations by setting the Configuration mode to "All Configurations." This ensures that the flag is set for all modes, including Debug, Release and Distribution modes.
- Check the case-sensitivity of "ObjC"; ("O" and "C" are uppercase, while "b" and "j" are lowercase).
Q. I'm not getting any ads. How do I start debugging?
A. Turn on logging by adding the QWSetLogging(YES) method in your application delegate before requesting ads. Then check the logs in your GDB console to look at the ad request and response and check any error messages.
Q. I am getting invalid pid / sid error message. What should I do?
A. There are two things that can cause this error:
- Invalid Publisher ID and Site ID: The correct IDs are listed on the Ad Tags tab when you download your SDK. Check your request against the IDs listed on the Ad Tags tab to ensure you’re sending the right IDs.
- Pointing to the staging environment rather than the production environment: Make sure your URL is pointing to the production environment (ad.qwapi.com), and not the staging environment (stg-ad.qwapi.com). To point to the production environment, you can call the following method: QWSetRunMode(QWProductionMode).
If neither of these work, then contact your Quattro Account Manager.
Q. What's this error message?
ERROR[4007]: Unable to resolve ad source. -- Unable to resolve ad source [adt] parameter
A. Ads may not be properly targeted for your application. Contact your Quattro Account Manager to ensure that ads are correctly targeted.
Q. What happens when the application is offline?
A. When the application is offline, no ads are rendered.
Q. Are any animations supported for rendering ads?
A. Yes. New ads are displayed using a default fade transition, where the existing ad fades out as the new ad fades in. No work needs to be done to use this normal transition.
QWAdView does support Core Animation layer transitions. The following example sets the new ad to slide in:
// set the animated transition CATransition *trans = [CATransition animation]; trans.type = kCATransitionMoveIn; trans.subtype = kCATransitionFromBottom; adView.adTransition = trans;
For more information on custom ad transitions and custom ad appearance, see the User Documentation included in the SDK package.
Q. When will I see conversion tracking data in Quattro’s reporting portal?
A. Data will be available within 24 hours from when the conversion is reported. The conversions will be recorded for the day the conversion happened.
Q. What inventory in the Quattro Network can display ads for my application?
A. Ads that advertise your application will only appear on other applications in Quattro's network. They will not appear on mobile sites.
iPhone Conversion Tracking FAQs
Please see iPhone Application Conversion Tracking FAQs.
Quattro Android SDK FAQs
Q. How do I change the background color of my ad?
A. Use the bgColor property of the XML API. It may be any value as defined Color.parseColor, for example:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:bgColor="green" />
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setBackgroundColor(Color.GREEN);
See http://developer.android.com/reference/android/graphics/Color.html for additional information on color values.
See Attribute Values for Android for additional information on the bgColor attribute.
Q. How do I change the text/link color for the text ad?
A. Use the textColor property of the XML API. It may be any value as defined by Color.parseColor, for example:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:textColor="green" /<
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setTextColor(Color.GREEN);
See http://developer.android.com/reference/android/graphics/Color.html for additional information on color values.
See Attribute Values for Android for additional information on the textColor attribute.
Q. Can I ask for text, banner and interstitial ads for the same ad spot/slot?
A. Yes, via the XML API you can set the mediaType property, and include multiple types.
See Attribute Values for Android for additional information on the mediaType attribute.
Q. I added the library but I am not getting any ads. Why?
A.
Q. I'm able to integrate with the Quattro Android SDK but I'm getting the same ads all the time. What should I do?
A.
Q. I'm not getting any ads on my app. How should I debug?
A. Debug messages are logged with the following tag: QuattroWirelessSDK/2.0. If the adView is not displaying ads then filtering based on this tag provides information about what the SDK is doing.
Q. I'm getting an Invalid SID, Invalid PID error in the log. What should I do?
A. Confirm that the publisherId and siteId that have been used to create the QWAdView are same as those values that were provided to you when you signed up with Quattro Wireless.
Q. I'm getting "No Qualified Ads" printed in my logs. What should I do?
A.
Q. Is there a user group where I can post my questions?
A.
Q. I want to plug into an external reporting product like Flurry. Does the SDK support this?
A.
Q. What kind of callbacks does the SDK support?
A. Callbacks are supported by implementing com.qwapi.adclient.android.view.AdEventsListener. The custom user generated class then may be registered via the XML API.
<lt;com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:adEventListenerClass="com.yourcompany.YourAdEventsListener" />
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
AdEventsListener listener = new YourAdEventsListener(); adView.setAdEventsListener(listener,false);
Q. How do I make the ads auto-rotate?
A. Use the displayMode property of the XML API. For example:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:displayMode="autoRotate" />
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setDisplayMode(DisplayMode.autoRotate);
See Attribute Values for Android for additional information on the displayMode attribute.
Q. Once the ad is displayed, I want it to fade away after 45 seconds. How do I do this?
A. Use the displayMode and adInterval properties of the XML API. For example:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:displayMode="aged"
qwad:adInterval="45" />
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setDisplayMode(DisplayMode.aged); adView.setAdInterval(45);
See Attribute Values for Android for additional information on the displayMode and adInterval attributes.
Q. I want to display my own default image when the Ad Server doesn't return any ads. How can I do that?
A. Use the defaultAdImage property of the XML API. For example:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="siteId"
qwad:publisherId="pubId"
qwad:mediaType="banner"
qwad:defaultAdImage="@drawable/sample"
/>
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setDefaultAdImage("@drawable/sample");
Q. How do I use the animation effects?
A. Use the defaultAdImage property of the XML API. This property takes an image ID format. In the example below, it assumes an image named sample has been placed in the drawable directory:
<com.qwapi.adclient.android.view.QWAdView
android:id="@+id/QWAd"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
qwad:siteId="itest3"
qwad:publisherId="b33eb94ffbce48bd8301a5476039cb63"
qwad:mediaType="banner"
qwad:defaultAdImage="@drawable/sample" />
You can also set this property via the java/non-XML API by obtaining a reference to the adView.
adView.setDefaultAdImage("@drawable/sample");
See Attribute Values for Android for additional information on the defaultAdImage attribute.
Q. Who should I contact if I need help?
A.
Q. How big is your SDK?
A. The size of the .jar file is 94.3 KB.
Q. Does your SDK do any caching?
A. The SDK caches ads if it is configured to use batch mode. In batch mode a single request is used to obtain a group of ads. These ads are cached and then served unless the group of ads is depleted.
Q. I want to get 10 ads at a time, display them, and then get 10 more ads. Can I do that?
A. See Attribute Values for Android for additional information on setting displayMode and mediaType in batch mode.
Q. I want only a specific type of ad. How can I specify that?
A. See Attribute Values for Android for additional information for on setting the mediaType attribute.
Q. How do I use the additional animation effects?
A. You can use them by copying the XML files in the res/anim directory of the SDK package to your projects res/anim directory. The additional animation effects hyperspace,push_left,push_up can then be used.
Q. Only Quattro test ads are being displayed. What am I doing wrong?
A. Ensure that the testMode attribute is set to false. testMode defaults to false if it is not provided.
Q. QWAdView is throwing exceptions upon startup. What's wrong?
A. Exceptions are thrown if the configuration of the adView is incorrect. If QWAdView is throwing an exception upon startup, look at the logcat file for an error message. The exception indicates which attribute failed and what value was provided.
Q. Can I use more than one QWAdView on a page?
A. Yes, by including more than one QWAdView on a page, more than one adView may be included on a page. These may be configured differently or the same depending upon user needs.
Q. How do I create my own custom ad events listener?
A. . A user can create a custom ad events listener by implementing the
com.qwapi.adclient.android.view.AdEventsListener. This class can then be registered with the adView that is created. Registering the custom events listener is done by setting the adEventsListenerClass to the class name. For example, adEventsListenerClass="com.example.YourCustomListener.
