# 动态添加属性说明

{% hint style="success" %}
SDK版本要求：**iOS 无埋点 SDK** >=2.x
{% endhint %}

## 1. UIView 增加属性

```java
// 手动标识该view不要追踪
// 不采集单个webView也用此属性设置
@property (nonatomic, assign) BOOL growingAttributesDonotTrack; 
​
// 手动标识该view不要追踪它的值，默认是NO，特别的UITextView，UITextField，
// UISearchBar默认是YES
// 对button、label无效
@property (nonatomic, assign) BOOL growingAttributesDonotTrackValue; 
​
// 手动标识该view的取值  比如banner广告条的id 可以放在banner按钮的任意view上
@property (nonatomic, copy)   NSString *growingAttributesValue; 
​
// 手动标识SDCycleScrollView组件的bannerIds  如若使用,请在创建SDCycleScrollView实例对象后,
//立即赋值;(如果不进行手动设置,SDK默认会采集banner的imageName或者imageURL)
@property (nonatomic, strong) NSArray<NSString *> *growingSDCycleBannerIds;
​
// 手动标识该view的附加属性  该值可被子节点继承
@property (nonatomic, copy)   NSString *growingAttributesInfo;
```

## 2. UIViewController 增加属性

```java
// 手动标识该vc的附加属性  该值可被子节点继承
@property (nonatomic, copy)   NSString *growingAttributesInfo; 
​
// 手动标识该页面的别名，对应"p"字段，不影响xpath生成，必须在该UIViewController显示之前设置
// 有些时候，对于完成某个功能的页面，统计时可能需要进一步细分。 比如，对于展示商品列表的页面，需要区分衣物类商品，以及食品类商品的两种列表的访问量。
@property (nonatomic, copy)   NSString *growingAttributesPageName;
```

## 3. WKWebView 增加属性

```java
// SDK版本2.8.22 开始支持
// 手动标识该WKWebView可以被采集，默认值为NO
// 使用场景：当enableAllWebViews设置为NO的情况下，需要采集该webView
// - 需要在initWithFrame:configuration:之后立即调用
// - 如果该webView.growingAttributesDonotTrack为YES，则此设置无效
@property (nonatomic, assign) BOOL growingAttributesIsTracked;
```


---

# Agent Instructions: 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:

```
GET https://growingio.gitbook.io/v3/developer-manual/sdkintegrated/ios-sdk/ios-sdk-api/dynamic-property.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.