# Tracking board columns changes

**URL:** <https://forum.asana.com/t/tracking-board-columns-changes/56856>\
**Category:** API & Developers\
**Created:** [5 August 2019 13:05 UTC](https://forum.asana.com/t/tracking-board-columns-changes/56856 "2019-08-05T13:05:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\
**Post date:** [5 August 2019 13:57 UTC](https://forum.asana.com/t/tracking-board-columns-changes/56856/2 "2019-08-05T13:57:29Z")

</div>

Hi @Fillipe,

Columns are `sections` in the Asana data model. So what you want to do is monitor changes in a project’s tasks and catch whenever a task’s section changes in that project.

### Monitoring changes in a project's tasks

This is done either via webhooks or monitoring events.

[Info on webhooks is here.](https://asana.com/developers/api-reference/webhooks)

[Info on events is here.](https://asana.com/developers/api-reference/events)

Note, though: if you’re going to use webhooks, the format of them is [changing over the coming month](https://forum.asana.com/t/asana-is-moving-to-string-ids-updated-with-revised-timeline/29340/28), so rather than using the above documentation for their data format, I’d recommend you set your app in the developer console to only use String IDs:

![image](https://us1.discourse-cdn.com/asana/original/3X/a/d/ad08d51bae077879fb2245df0039f81f0fc6b458.png)  
and then use [the new data format that’s described here](https://forum.asana.com/t/asana-is-moving-to-string-ids-updated-with-revised-timeline/29340/11).

### Catch whenever a task's section changes in that project

This is done by monitoring a task’s `memberships` array property. (For info, see [the description of the memberships property here](https://asana.com/developers/api-reference/tasks).) Each membership is a combination of a project and a section in that project. So whenever you get a task-change webhook/event for a project’s task, you would locate the membership array element for that project and grab the section (if any). You’ll need to store those sections in your own data store along with the `created_at` timestamp for that webhook/event.

By comparing the section you stored with the current section in the webhook/event payload, you’ll be able to know that the section changed. By using the timestamp you stored vs. the current timestamp of the webhook/event, you’ll be able to calculate how long the task resided in a given section.

---

_[View the full topic](https://forum.asana.com/t/tracking-board-columns-changes/56856)._