Kenny/ Campaign docs revamp

[KennyHuRadar]

The campaign docs are quite stale, pulling in elements from the following PRs to create a consolidated PR for our new campaign offerings.

• https://github.com/radarlabs/documentation/pull/602/files
• Kenny/campaign user tag targeting #630
• Android deep linking note #624
• Campaign Builder Doc #595

What?

Why?

How?

Screenshots (optional)

Anything Else? (optional)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
documentation	Canceled			Aug 19, 2025 8:15pm

[Copilot]

Pull Request Overview

This PR consolidates campaign documentation updates from multiple previous PRs to revamp the stale campaign documentation, bringing it up to date with current campaign offerings and features.

Key changes include:

• Added comprehensive documentation for user tags functionality across iOS and Android SDKs
• Expanded campaign types to include in-app messaging, beacon notifications, and event-based notifications with detailed implementation guides
• Enhanced targeting options with advanced user targeting, beacon region targeting, and location authorization targeting

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
docs/sdk/ios.mdx	Added user tags API documentation with Swift and Objective-C code examples
docs/sdk/android.mdx	Added user tags API documentation with Java and Kotlin code examples
docs/campaigns.mdx	Major overhaul including new campaign types, targeting options, analytics setup, and deep linking configuration

Comments suppressed due to low confidence (2)

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[ShiCheng-Lu]

should be

class MyRadarInAppMessageDelegate : RadarInAppMessageDelegate {
    // Called when the CTA button is clicked by the user. Default behavior open configured deeplink, override to implement custom behavior
    override func onInAppMessageButtonClicked(_ message: RadarInAppMessage) {
       ...
    }

    // Called when the dismiss button is clicked by the user. Override to implement custom behavior
    override func onInAppMessageDismissed(_ message: RadarInAppMessage) {
      ...
    }

    // Called just before the SDK displays the in app message. The return values decides if the in app message is displayed or discarded
    override func onNewInAppMessage(_ message: RadarInAppMessage) -> RadarInAppMessageOperation {
      ...
    }

   // Called to create the in-app message view. Default behavior creates a view defined by Radar, override to create a custom view. (note: if a custom view is used, the dashboard preview will not be accurate)
    override func createInAppMessageView(_ message: RadarInAppMessage, onDismiss: @escaping () -> Void, onInAppMessageClicked: @escaping () -> Void, completionHandler: @escaping (UIViewController) -> Void) {
      ...
      completionHandler(viewController)
   }
}

and we can probably make this a code tab, and include ObjC as well

[ShiCheng-Lu]

ObjC:

// .h file
#import <Foundation/Foundation.h>
#import <UIKit/UIKit.h>

#import "RadarSDK/RadarInAppMessageDelegate.h"

// The member methods can be optionally defined to use custom behavior, or left out to use default behaviour
@interface MyObjC_IAMDelegate : RadarInAppMessageDelegate

// Called when the CTA button is clicked by the user. Default behavior open configured deeplink, define this function to override default and implement custom behavior
- (void)onInAppMessageButtonClicked:(RadarInAppMessage * _Nonnull)message;

// Called when the dismiss button is clicked by the user. Override to implement custom behavior
- (void)onInAppMessageDismissed:(RadarInAppMessage *)message;

// Called just before the SDK displays the in app message. The return values decides if the in app message is displayed or discarded
- (RadarInAppMessageOperation)onNewInAppMessage:(RadarInAppMessage *)message;

// Called to create the in-app message view. Default behavior creates a view defined by Radar, override to create a custom view. (note: if a custom view is used, the dashboard preview will not be accurate)
- (void)getIAMViewController:(RadarInAppMessage * _Nonnull)message completionHandler:(void (^)(UIViewController *))completionHandler;

@end

// .m file
@implementation MyObjC_IAMDelegate

- (void)onInAppMessageButtonClicked:(RadarInAppMessage *)message {
}

- (void)onInAppMessageDismissed:(RadarInAppMessage *)message {
}

- (RadarInAppMessageOperation)onNewInAppMessage:(RadarInAppMessage *)message {
    return RadarInAppMessageShow; // or RadarInAppMessageIgnore
}

- (void)getIAMViewController:(RadarInAppMessage * _Nonnull)message completionHandler:(void (^__strong)(UIViewController *__strong))completionHandler {
}

@end

[ShiCheng-Lu]

should inherit from RadarInAppMessageDelegate

[ShiCheng-Lu]

need some changes on the prefered way to use RadarInAppMessageDelegate, I've provided the code snippets for swift and ObjC, I think we should also use the tab items for the In app messaging section.

Besides that, other changes looks good.

[lmeier]

why are we changing this to code snippets?

[lmeier]

Let's link to the docs instead: https://docs.radar.com/beacons

[lmeier]

I think we want a section "Client-side notifications (iOS only)" with subsections for geofence/place and then for beacon based

[lmeier]

clientside beacon are ios only and belong above. but there's beacon event notifications that fit here

[lmeier]

You say "no additional code is required" and then present a bunch of code snippets. Give an intro to life cycle hooks and when someone would want to use them

[lmeier]

"Custom styling"?