> For the complete documentation index, see [llms.txt](https://doc.appflow.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.appflow.ai/docs/sdk-set-up-instructions/ios-sdk/event-tracking-custom-events.md).

# Event tracking (Custom events)

***

### **First installation**

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .firstOpen, params: nil)
```

### **The App launched**

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .appStart, params: nil)
```

### **The App current uv**

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .screenView, params: [
    kScreenViewName: kHomepage
])
or
let model = ParamModel()
model.screenType = ParamScreenHome
Appflow.shared.analytics.uploadBigDataWithType(eventType: .screenView, paramModel: model)
```

### **Ads click**

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .adsClick, params: [
    kPlacement: kQuickClean,
    kFormat: kBanner
])
or 
let model = ParamModel()
model.placeType = ParamPlaceClean
model.formatType = ParamFormatBanner
Appflow.shared.analytics.uploadBigDataWithType(eventType: .adsClick, paramModel: model)
```

### **Ads show**

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .adsShow, params: [
    kPlacement: kQuickClean,
    kFormat: kBanner
])

let model = ParamModel()
model.placeType = ParamPlaceClean
model.formatType = ParamFormatBanner
Appflow.shared.analytics.uploadBigDataWithType(eventType: .adsShow, paramModel: model)
```

### **ev\_User\_Engagement**

```swift
let tMSimestamp = "\(IMDeviceInfoManager.shared().getCurrentMSimestamp())"
Appflow.shared.analytics.uploadBigDataWithType(eventType: .userEngagement, params: [
    kEngagementTimeMsec: tMSimestamp,
    kScreenViewName: kHomepage
])
or
let tMSimestamp = "\(IMDeviceInfoManager.shared().getCurrentMSimestamp())"
let model = ParamModel()
model.screenType = ParamScreenHome
model.otherData = [
    kEngagementTimeMsec: tMSimestamp
]
Appflow.shared.analytics.uploadBigData(eventType: .userEngagement, paramModel: model)
```

\*\*If you need a callback in the above method, do something like this

```swift
Appflow.shared.analytics.uploadBigDataWithType(eventType: .userEngagement, params: [
    kEngagementTimeMsec: tMSimestamp,
    kScreenViewName: kHomepage
], successBlock: { obj in

}) { obj in

}
```

\*\*If the above enumeration does not meet the requirements, extend it as follows

Swift

```swift
Appflow.shared.analytics.uploadBigDataWithEvent(
    eventName: "event_name",
    params: [
        "name": "123",
        "time": "456"
    ])
```

For now, we have limited the number of Custom events you can send to Appflow\.ai. The current limit is **10** custom events per app. To register them you need to go to Settings=> Apps=> Edit app=> Add custom events

<figure><img src="/files/f1bm5QCuAY8FQ7V6Oa9r" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.appflow.ai/docs/sdk-set-up-instructions/ios-sdk/event-tracking-custom-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.